Show Notes
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
More from Beyond Coding
How do senior engineers use coding agents on prod infrastructure when “make no mistakes” is just a polite request? Kerim Satirli (HashiCorp, an IBM company) explains why prompt rules don’t hold in production, and what he runs instead. In this video, we cover: How Infrastructure as Code (Terraform, Contentful, Datadog, Okta, Cloudflare providers) evolved from open-source PRs to automated agent harnesses Why AI skills files and “make no mistakes” prompts are only requests, and what replaces them in production pipelines How AI-generated pull requests are overwhelming open-source maintainers (and why projects like cURL are pushing back) Personalized “software factories”, spec-driven development (GitHub Spec Kit), and cutting AI documentation noise with BLUF (Bottom Line Up Front) What open-source Rust clones of Adobe mean for the future of SaaS For infrastructure engineers, DevOps practitioners, and software architects who want to move past one-shot prompting and run coding agents on production infrastructure without losing control. Timestamps: 00:00:00 - Why “Make No Mistakes” Is a Polite Request 00:00:38 - How Open Source Terraform Changed Provisioning 00:01:59 - Why API-First Services Matter Beyond AWS and Azure 00:04:19 - How AI Agents Changed Terraform Provider Updates 00:07:03 - Why “Make No Mistakes” Won’t Stop Your Agent 00:10:31 - Bringing Determinism Back to Agentic Workflows 00:13:07 - How AI Pull Requests Are Overwhelming Open Source 00:15:41 - Why Every Engineer Is Building a Software Factory 00:18:52 - Why AI-Generated Documentation Slows Down Humans 00:23:12 - Using Agents to Filter Noise and Summarize Specs 00:27:02 - Escape Hatches for Automated Terraform Applies 00:29:03 - Where the Joy in Engineering Lives Now 00:31:24 - Spec-Driven Development and the Return of Architecture 00:34:51 - Open-Source Rust Clones, Reverse Engineering, and SaaS 00:38:19 - How to Build Software Products People Actually Want
Lead Architect Carlos Kelkboom shares his rules for coding agents and how great engineers architect software with AI. One of the great ones is: he throws away generated code the moment he doesn't understand it. He breaks down why coding agents fail at iterative changes, why his main agent never touches files, and how he scaffolds projects for one-shot execution. In this video, we cover: Why AI coding agents struggle with iterative changes (SlopCodeBench) and excel at one-shot execution How to manually scaffold code, types, and folder boundaries before letting sub-agents run Designing a distributed Markdown and indexed-search graph harness for progressive context disclosure Using Git worktrees to run parallel coding agents and merge the best implementations Why dynamic memory and the heap need to disappear in favor of deterministic programming languages How AI bubbles and solo coding impact junior engineers and team collaboration This episode is for software engineers, tech leads, and system architects who want to move beyond "vibe coding" and build maintainable, deterministic production software with AI agents. Connect with Carlos: https://www.linkedin.com/in/carlos-k-4016b8225
What happens when coding agents see your entire system: code, services, infrastructure and live traffic, all connected? Most agents are blind to everything outside the repo. Adyen Staff Engineer Mat Jones explains what changed once theirs weren't, and why he calls it somewhat scary. In this video, we cover: Running five or six coding agents in parallel with git worktrees and Atrium, an internal tool that lets agents coordinate and share memory Architect: nine connected graphs in Neo4j covering services, code, DNS, data stores and infrastructure Ingesting 7 million trace spans a second with Kafka and Apache Flink, and what collapsed on the first try Sentinel: anti-pattern monitoring, with agents that raise the fix as a merge request MCP vs APIs vs CLI tools, and how to deal with tool bloat This episode is for software engineers and platform teams who want coding agents to reason about real systems, not just the repo in front of them. You'll leave with a concrete place to start and an honest view of the risks.
HumanLayer CEO Dexter Horthy, who coined "context engineering", on why AI agents degrade codebases over time. He breaks down a benchmark that measures AI code quality across features, and how his team ships with agents without drowning in slop. In this video, we cover: SlopCodeBench, SWE-bench and which coding benchmarks to trust Token maxing, dark factories and the "Instagram phase" of AI engineering Why 2-4x productivity beats chasing 100x Pull requests, design docs and how engineers build taste now Dex's agentic engineering workflow: one-shots, overnight janitor bots and research-design-plan For engineers and engineering leaders adopting AI coding agents who want to know what's real and what works in teams at scale. Timestamps: 00:00:00 - The Man Who Coined the Term: Context Engineering 00:00:54 - SlopCodeBench: Proof AI Makes Codebases Worse Over Time 00:05:49 - Background Agents and the Enterprise Friction Problem 00:08:13 - Why You'll Never One-Shot a Big Feature 00:11:18 - Scaling Agentic Engineering to 1,000 Engineers 00:16:19 - Dark Factories, Fake Hype and Token Maxing 00:19:55 - Why 2-4x Faster Beats Chasing 100x 00:21:31 - Should Teams Stop Doing Pull Requests? 00:24:20 - Can Deterministic Tools Replace Code Review? 00:27:37 - How to Build Engineering Taste When AI Writes Code 00:33:05 - Dex's Agentic Workflow: One-Shots and Janitor Bots 00:35:18 - Research, Design, Plan: Shipping Big Features With Agents 00:38:35 - Why Overnight Agents and Heavy Parallelism Backfire 00:40:10 - Subscription Maxing vs Paying Per Token 00:42:40 - Parallelize Like Poker, Not a Slot Machine Dex Horthy: https://x.com/dexhorthy Dex's talks and deep dives: https://aithatworks.bold.video #AgenticEngineering #AICoding #SoftwareEngineering
Amp ships to production around 50 times a day with AI agents, but the change that makes their team ship faster isn't AI at all. Dario Hamidi, AI engineer at Amp, makes the case that pull requests are holding your team back, and explains what replaces them. In this video, we cover: Why Amp works without pull requests or feature branches, and how to try it with your own team Agent permissions, approval fatigue, and building environments where you can trust agents Orbs: remote agent execution, parallelism, and multiplayer sessions Short-lived credentials and workload identity federation for cloud agents Triaging 60+ bug reports a day with agents without frying your brain For engineers and engineering leads who want to ship faster with AI agents and are ready to question the workflows they've always used. Timestamps: 00:00:00 - Is It Time to Kill the Pull Request? 00:00:45 - What Happens If Every PR Gets Auto-Closed Tomorrow 00:05:04 - Pull Requests Were Built for Strangers, Not Teammates 00:07:20 - Does Dropping PRs Hurt Quality at Scale? 00:08:53 - Agent Permissions: Why No Default Makes Everyone Happy 00:12:42 - Don't Juggle Knives: Building Environments You Can Trust 00:14:56 - The Hidden Hard Parts of Cloud Agents 00:16:39 - What's an Orb? Remote Agent Execution Explained 00:19:10 - How to Give Agents Credentials Without Leaking Secrets 00:22:51 - Why Orbs Live Forever (and Multiplayer Orbs) 00:25:49 - The State Management Problem Nobody Talks About 00:29:22 - When Will Everyone Have Remote Dev Environments? 00:32:23 - Orbs That Spawn Orbs: Orchestrating Agents at Scale 00:34:42 - How Dario Triages 60 Bug Reports a Day With Agents 00:39:23 - Avoiding Burnout When Agents Remove the Ceiling #AIAgents #SoftwareEngineering #PullRequests