FizzBuzz Enterprise Edition VS yGuard

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...