Today, we’ll talk about design patterns and some of the best online courses to learn design patterns in Java. If you are wondering what a design pattern is and why Java developers should learn them, then let me give you a brief overview.
In simple terms, design patterns are nothing but a tried-and-tested solution to common programming problems, for example, the creational design patterns deal with the problems of object creation.
Sometimes, when an important project is going poorly there’s a desire to start over. Sometimes this comes from management but often this comes from the developers themselves. They say if they only had a second chance and could start over then they can build the right system.
But that almost never happens. Take it from me. I’ve seen companies try many times and I can say that without exception, when a team sets out to rebuild the same system with basically the same approach, they end up with roughly the same system the started with, including the same problems only this time they have two systems they have to maintain.
There is a simple principle for naming methods in OOP. I’m trying to demonstrate this in the following code — it’s a verb if it manipulates; it’s a noun if it builds. That’s it. Nothing in between. Methods like saveFile() or getTitle() don’t fit and must be renamed and refactored. Moreover, methods that "manipulate" must always return void, for example, print() or save(). Let’s take a closer look!
The Night Of (2016) by Richard Price et al.
