Skip to main content

Devoxx 2025 - Outcoded by our kids

Last week, I had the pleasure of attending Devoxx 2025 as a speaker. I didn't know what to expect as this was my first Devoxx experience.

Together with Jan Van Wassenhove, I presented on being an AI-native developer:

Outcoded by Our Kids: It Took Us 20 Years, They Used 20 Prompts!

What took us two decades—learning frameworks, debugging builds, arguing about folder structure—took our kids… 20 prompts.
This is the painfully real story of two tech dads—Jan and Bart—whose 11 and 12 year-old sons built games using agentic platforms. With no coding experience, they created levels, enemies, sounds, and score systems by simply describing what they wanted. No IDE. No syntax errors. Just intent, interpreted by a growing wave of AI agents.
In this talk, we contrast their lightning-fast creative process with our traditional, structured dev mindset. We showcase their games, break down how these tools work, and explore what this means for software development.
Some key questions we asked ourselves:

  • Are we witnessing the end of traditional programming?
  • Are we still relevant as architects, developers, and engineers?
  • What roles and skills matter in a world of AI-assisted, no-code creation?
  • How do we move from being builders to being orchestrators?
Funny, humbling, and deeply relevant—this session is for every dev who's ever thought, "That’s not how we used to do it..." And for those who are ready to embrace what’s next.

We brought our kids along (after all, they did all the hard work!). What I didn't expect was that we'd get a full behind-the-scenes tour from Stephan Janssen, the Devoxx founder himself. If I hadn't already succeeded in getting my son interested in STEM, Stephan's stories and enthusiasm certainly did!

Needless to say, our kids had the time of their lives.

The talk is already available on YouTube—check it out:

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more