Why New Isn’t Always Better
in Software Development
New is always better! You might get this impression if you deal with various aspects of software development and operation. But that is definitely not the case. Often a course correction of 180° is not necessary. Sometimes just a little twist is enough.
🫵 Programming language A is better than B. We can all only use B. All other solutions are insecure, not performant
enough, not maintainable, and prone to errors.
🤔 But in reality we should change the way we work. You can write good and bad code with ANY programming language. The
real problem? Poorly tested code, quick hacks and no ongoing maintenance.
💡 Learn the right way of working and it will deliver better solutions in any environment.
🫵 Architecture X is bad. The only solution is architecture Y.
🤔 But what you’re usually really trying to achieve is a modular, maintainable solution. Still open to taking advantage
of individual scaling benefits.
💡 Combine different approaches to create a practical solution to solve your specific problem. As a rule, there is
rarely THE one ultimate solution for everything.
🫵 My infrastructure surpasses yours. Follow me if you want to win.
🤔 You just want to create a stable, low-maintenance environment. Which is cost-efficient, expandable and requires
little manual effort.
💡 There are now countless solutions that open up great possibilities for you. What suits you? Compare the
advantages/disadvantages carefully. Make a conscious decision.
Niche solutions in particular often generate little noise in articles or videos. You have to be really interested in it to get to know a seemingly unknown approach that is ideally suited to your problem. And even programming languages or frameworks are often selected based on their status in surveys.
Know your field! Be curious! Work with tools that didn’t make it into the top 10. You will find that the possibilities are incredibly diverse.