Projects to see some concepts discussed on main documentation
Whenever the piece of code goes fast to production, following previsible, boring standards of quality and style, it can be called enterprise.
This is important because it indicates that we're not coding to explore a new concept or to sample something in a academic paper. We're making money, not art.
To achieve speed, a high degree of code reuse is advised. The DRY is paramount here.
Thanks to Open Source, mostly in the form of Apache Foundation, enterprise java flourished and thrived, making it one of the most prominent ecosystem able to support this kind of solution.
One would argue that enterprise code is also testable code. Although this is highly desirable, it's not a rule easily seen out there. In tis guide we'll cover tests because it builds up our trust in the delivered code.
Quality and style are historically solved by someone's opinion transmuted into a standard, like SOLID (or GRASP before that), and tooling like style checkers, formatters and, of course, test and coverage tools.
Every project folder has a README.md with minimal instructions. Depending on the project, it can be just a few terminal commands using the interpreter or the compiler directly, or detailed instructions on how to spin a container or compose IaC file.
The README file will often explain:
- Dependencies
- How to build/compile
- How to execute/test
- Present a small noteworthy list of interesting trivia
- Sometimes there are exercises to perform
Go from the first project to the last one, they are numbered to help on that. Each project will introduce a new concept which might or might not appear again in the next one, but will be useful when building other things.
When reading the docs, there will be links to the sample projects, so read de guide and it will kick you into the samples time to time.