The Open Closed Principle is responsible for the 'O' of the S.O.L.I.D principles. Originally coined by Bertrand Meyer, it states that:
Software entities (classes, modules, functions, ...) should be open for extension but closed for modification
It seems like an incredibly simple principle, but it's behind most
The Single Responsibility Principle is probably the most confusing of all 5 S.O.L.I.D principles. It took me quite a while to understand why it's an important thing, and where to apply it. The phrasing has changed through the years, but in most places, you will find
When your program starts running in production, the conditions and cases you thought impossible will happen, period. In reality, it's impossible to ensure that your code will have optimal running conditions all the time. As a developer, you'd like to ensure your projects will be able to cope with the
There are only two hard things in Computer Science: cache invalidation and naming things
_Phil Karlton
Despite being one of the easiest ways of improving the quality of code, writing good variable names is perhaps the most overlooked skill in a developer's toolbox. Sharpening your naming chops is a sure
If it walks like a duck and it quacks like a duck, then it must be a duck
We saw in a previous article that it's much better to depend on abstractions than on concrete classes. Concretions are more likely to change than abstractions, and those changes will ripple through