Veteran Architect: How To Design And Build Systems That Survive

What separates software that survives from software nobody wants to touch? Nico Krijnen has spent 30 years building systems, coaching teams, and learning why some projects thrive while others quietly become the legacy code everyone avoids. In this episode, he shares why the real work starts after you ship, what actually turns a system into legacy, and why the knowledge in your team's heads matters more than the code itself. In this episode, we cover: Why production is where the real learning begins The team composition that consistently delivers results Peter Naur's Theory Building and why documentation alone falls short How knowledge leaving your team turns working systems into legacy Why assuming you're wrong leads to better architecture Whether you're a senior engineer rethinking how you build or earlier in your career trying to understand what really matters, this episode will change how you think about software that lasts. Connect with Nico: https://realworldarchitect.dev TIMESTAMPS 00:00:00 - Intro 00:01:17 - Why He Keeps Choosing Engineering Over Management 00:04:01 - Three Seniors Solved in Three Weeks What Management Couldn't 00:05:14 - The Signals You Miss When You're Not in the Team 00:06:26 - The #1 Skill Behind Every Successful Project 00:08:04 - Why Production Is the Starting Line, Not the Finish 00:10:13 - The Habit Most Teams Skip After Deploying 00:11:28 - Why the Best Teams Mix Designers and Engineers 00:14:36 - Finding the Right People for the Job at Hand 00:17:01 - What Juniors Bring That Seniors Can't 00:20:57 - How to Handle Ideas You Disagree With as a Senior 00:24:21 - A Simple Technique to Surface Everyone's Best Ideas 00:27:09 - What Makes a System Survive Long-Term 00:30:53 - What Actually Makes a System "Legacy" 00:35:01 - The Knowledge That Keeps Software Alive 00:36:06 - Peter Naur's Theory Building: Why Documentation Isn't Enough 00:40:06 - How Knowledge Loss Is Killing Your Codebase 00:42:42 - The Hidden Risk of AI Tools for Team Knowledge 00:48:14 - Why You Should Assume Everything You Build Is Wrong 00:51:31 - Make Hard Things Easy to Change #SoftwareEngineering #SystemDesign #TechPodcast