Less Is More

The sentence is not mine, I took it from famous architect Mies Van der Rohe. But I have made it my motto for years. I have been working in the IT industry for about two decades now and I even started coding on my Commodore C64 in the mid-80s. Things are changing at the speed of light in the industry. Not always for the better.

Object-Oriented Programming, design patterns, microservices, devops are all great things … when they are really understood. I have seen so many developers adding useless complexity in their code just because they vaguely remembered that this pattern had to be used in their precise case. I remember one of my colleagues who had spent a few hours automating the installation of the database server. We never used his script because he had created the two needed servers while fine-tuning his script. So many guys do things because they read on the web that this is a best practice. But they are not able to answer a simple why question.

Make things simple, go straight to a working version. Test it, clean it, refactor it. Then only, if what you did is too simplistic, doesn’t support the expected load, or any other reasons, it won’t be complicated to add some sophisticated patterns because they will help you solve your specific issue. But please do not solve the problems you don’t have just because they might occur.