tutorials VS FizzBuzz Enterprise Edition

But ok, lets try with this example, line 40 : https://github.com/eugenp/tutorials/blob/master/testing-modules/junit5-annotations/src/test/java/com/baeldung/junit5/nested/OnlinePublicationUnitTest.java This code tests a function which is 5 lines long, called only once. It doesn't even deserve a method declaration, this is complexity for the sake of testability. 6 months from now, when you look for articles filtered by user membership, you are not going to find this function. You will be lost in a maze of method declarations. Fragmenting your execution flow is a bad idea, especially for testability purposes. The test code is even more complex than the code being tested.

Baeldung has a lots of tutorials... GitHub - WebModules

You can checkout more examples on below GitHub Repository. https://github.com/eugenp/tutorials/tree/master/json-modules/json-2

I found an example for you online: https://github.com/eugenp/tutorials/tree/master/docker/docker-spring-boot-postgres

git clone https://github.com/eugenp/tutorials.git

The best way is to find a job, write horrible code, get absolutely humiliated on the MR and then you will start getting all that stuff. A second option would be to read code from others, I always keep this repo open https://github.com/eugenp/tutorials.

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

Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.

Bu hocam https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition

amidoingitright

It seems to me that all large software projects eventually grow into "Enterprise" code. What I mean by this is something like FizzBuzz Enterprise Edition; large codebases with many layers where Design Patterns and SOLID principles are applied vigorously.

???

I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)

I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P

In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.

C++? No bloat*, just speed

*Yes, there's some _optional_ bloat. But compared to Java? no contest.