FizzBuzz Enterprise Edition VS Java-Hello-World-Enterprise-Edition

To make sure we're really working with Java, look at some short class names:

Java encourages (partly through language design and partly through its community/ecosystem) [Enterprise Grade Programming](https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...). The problem isn't the language per se, but that most code bases will require you to earn an architecture astronaut certification for that particular code base.

But also, the Go spec is a couple of pages and the Java spec is, uh, it's taking a while to load for me... ah yes, 876 pages. How's that learning curve?

It gets worse (this isn't too much of an exaggeration): https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris....

As an undergrad, I once spent about half an hour peer programming with a computer science PhD - it was enlightening.

He didn't have the slightest understanding of software - calling me out for things like not checking that the size of a (standard library) data structure wasn't negative.

Sometimes there's a scary lack of understanding and competency where you'd expect to find it.

Sometimes these things are done for a reason; sometimes it's actually sane and sometimes it's just a way to deal with the lunacy of a codebase forged by the madmen who came before you.

Now if we have all the time in the world, we can make the thing as complicated as we like: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition.

In code, this means you must have clear separation of concerns, so future changes are less likely to require scattered changes throughout your code base. Clean Architecture is a certified classic for this subject, just remember to not overdo it in the wrong area and end up with Enterprise Edition FizzBuzz.

That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

If you judge productivity by lines of code, absolutely.

https://github.com/Hello-World-EE/Java-Hello-World-Enterpris... is an excellent demonstration of this.

This reminds me of the "enterprise programming" mindset in OOP where people would make factories, strategies, strategy factories etc. just for the sake of it (instead of those solutions serving a real need) and ending up codebases that look like Hello World enterprise edition.

No other language or framework seems to get the same scrutiny as JavaScript.

The Enterprise Java solutions never seem to get as much discussion but we all recognize it also as being equally if not more so absurd[1]. This is true of every language and framework that gains mass adoption and use. Scala projects are crazy complex, the python 2 to python 3 migration was a mess, none of these are problems. They reflect the improvements in every metric to the underlying platforms and systems - end user experience, developer experience, reliability, testability etc.

JavaScript is in a phenomenal place today - we have come "full circle" but with better tooling, new capabilities, improved experiences etc.

There's a lot of keeping up with the jones' - that's partly nice as its job security and partly nice as a reflection of engineers improving our own ecosystem.

[1] https://github.com/Hello-World-EE/Java-Hello-World-Enterpris...

It’s bad, but not as bad as the enterprise edition

Hello World Enterprise Edition - https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition

You might actually have to think about writing longass assembly hello world, but I can spin up fifteen Enterprise Java Hello World APIs in an afternoon.

Haven't written Java in years, but I'd take an enterprise edition program written in it, much like this one: https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition