Design patterns are famous because they offer optimal solutions to usual software creation issues. In the same way, many habits are common in software creation while not being optimized. That’s why best practices exist: share with all a way to do things that seems better than others in most cases. And since it’s about sharing, the blog seems to be a good place.
A few weeks back, I reviewed code from a young developer.
It was impressive work for a topic he didn’t know beforehand, except on one aspect: every output used System.out.println().
That’s understandable: that’s how Java developers learn to code, just like Python developers do their first tests with print.
But that’s not something that’ll be handy for a live application.
If you’ve been using Spring for a while, or copy-pasting some web tutorials or examples, you’ve probably put some @Autowired annotations on private fields.
This does work, but it’s not the best way to do it.