Software Engineering

A software system that remains maintainable for many years and continuously generates business value, requires some planning, development and maintenance. When choosing the underlying technologies, we often notice, how important it is to choose technologies based on their maturity rather than just following current trends (Boring Technology). Because clearly, any technology is only as good as the problem it solves.

As requirements evolve and software must respond to changes, it will inevitably accumulate technical debt. But not all technical debt is the same. And is that the same as legacy code? Not quite, but in the end, what matters most is: How much effort does it take to maintain the system? (Technical debt and legacy code) .

How to reduce technical debt? First, technical debt is also a management problem (Technical debt - despite its name - is not a purely technical problem). But also on an individual level, a certain mindset based on commitment, humility and empathy is necessary (The mindset for long-living software systems).

In our experience, a combination of Blueprints and the Scout Rule has proven successful (Tech-Debt Dilemma). A classic worth reading is Working with Legacy Code by Michael Feathers.