Skip to content

Mastertutorial · Part 6

How does modern system development work?

With Christian Liebich23 minSystems & architecture

In short

Modern software development builds on cloud, microservices, APIs and SaaS. AI is a strong assistant in it, but no replacement for developers and architects: it delivers code fragments and knowledge, not a complete system. Software is the institutional memory of the business processes. Whoever lets the people with that knowledge go loses the understanding of their own use cases.

The video is spoken in German and has integrated English subtitles. The podcast episode and the blog article are in German. This page summarises the episode in English.

The video is loaded from YouTube only after you click. Data is then transferred to YouTube.

What you take away

  • Use AI as a multiplier, not as a replacement for expertise.
  • Programming is only around 20% of the effort. The rest is solution design, requirements and process understanding.
  • Rule of thumb: an application that has been in use for ten years is old and usually has to be rewritten.
  • “Never touch a running system” no longer holds: outdated systems are a security risk.

Topics of this episode

  1. The AI myth: why developers remain irreplaceable
  2. Looking back at 1999–2013: HTML5 and bandwidth
  3. From 2017: MVC, microservices, APIs and SaaS
  4. Cloud, apps and blockchain
  5. GenAI between reality and hype
  6. The legacy dilemma
  7. The 80/20 rule of transformation

Who it is for

For executives and investors without deep technical knowledge who have to judge IT strategy and development costs for the coming years.

This episode as

Related service

Solution & System Architecture

Target architecture, tech stack and reviews, so that your software stands on a foundation that still holds in five years.

Frequently asked questions

Will AI replace software developers?

No. AI generates fragments for individual modules and provides knowledge very quickly, but it does not replace the understanding of system architecture and business processes.

When is an application outdated?

As a rule of thumb after around ten years in use. Lifecycle management can delay this, but at some point the application has to be rewritten.

Why is waiting risky with legacy systems?

Attackers use AI too and find weaknesses in outdated libraries faster. Added to that are lost productivity and the difficulty of finding specialists for old technologies. The longer you wait, the more expensive the replacement becomes.

All Mastertutorials

Let us talk about your project

A first conversation takes 30 minutes and is free of charge. Afterwards you know which next steps make sense.