There is only one predictable property in our job as software developers: it is change. Unfortunately it is not predictable enough, you can bet it will happens, but you cannot say when and how. This lead us to a simple question, how can I write code that embraces change?
This month I started a serie of blog posts about this topic on my current company blog. These are not new concepts, but looking back I can say these small principles made a big step into my coding mindset.
The first article discusses how simply wrapping an instance variable in a method has deep and useful consequences on the maintainability of your class. Dependencies are always a mess to deal with.