Software-Quality

Change is a constant factor in the IT-sector, as its driven by technological innovation. Thus, software-quality has gained importance as IT-landscapes tend to grow, to still be able to hold up high SLAs.

• Mitigating technical debt: My approach to software-design is "simple, not easy". Software should solve complex problems in an elegant way; "quick and dirty" solutions convert working software to "legacy"-system within just a few months.

• High Test-Coverage: Testautomation cannot be replaced with anything but more tests. A lot of things can go wrong with a deployment - an error in the software's logic should not be one of them.

• Longterm Maintainability: Despite a common misconception, software is written for people, not machines. In contrast to machines, which usually don't mind running undocumented spaghetti-code, people usually don't like working this way - thus, I always have the "real audience" in mind when writing software.

• Routine Deployment: Releasing a new Software-Version should not be "a thing". By adopting modern DevOps-Paradigms, shipping the latest version to the customer can become a routine - without gathering all developers in the main meeting-room.