Podcast profile
By Henry Suryawirawan
Great technical leadership requires more than just great coding skills. It requires a variety of other skills that are not well-defined, and they are not something that we can fully learn in any school or book.
Latest episode
59 min
Topics
Managing engineering organizations, teams, delivery, architecture, and technical leadership.
Hiring, career development, skills, workplace practice, and professional progression in technology.
Developer productivity, tooling, workflows, platforms, and engineering enablement.
Formats
Detailed technical, architectural, or research-oriented examination.
Host-led conversation where a guest supplies most of the subject matter.
Audience level
Assumes basic technology literacy and familiarity with common products, roles, and terminology.
Stay connected
From the feed
Episodes shown — 10 of 25
What’s the one rule that matters most when AI writes most of your code? Emilie says it comes down to a single line: don’t outsource your thinking. In this episode, Emilie Schario, co-founder of Kilo Code, unpacks what it actually means to lead in a world where AI can write most of your code.
If you’re not using AI five times an hour, you’re already behind, says the man who built the first AI assistant back in 1998. Kevin explains why that pace is now the baseline, not the exception, for developers who want to stay employed.
Does moving faster with AI mean you get to skip the laws that governed every software project before it? Milan Milanovic argues the opposite, the old laws of software engineering now apply twice as hard.
SpeechifyAI's new Simba 3.2 model ranks #1 on Artificial Analysis for realness, priced under $10 per million characters. Building something conversational? Why do the same software delivery illusions keep fooling smart engineering teams?
Is vibe coding quietly draining the thing that makes teams effective: their shared understanding? Margaret breaks down her new “triple debt” model, and why cognitive debt might be the one nobody’s tracking.
If expertise is becoming almost free, why is judgment becoming the most expensive skill in tech? Ajey Gore, former Gojek CTO, explains why the age of AI agents rewards builders over typists.
What if optimizing for AI output is actually slowing your company down? When code becomes nearly free to produce, the organizations still measuring productivity by output are solving the wrong problem.
Why do 70% of change efforts fail — even when leadership is fully committed? The answer isn’t strategy or resources; it’s the hidden stories people unknowingly carry that silently block every initiative.
What if your AI coding agent is quietly cheating on your tests — and how do you stop it? Julien Verlaguet, who built the type system Meta used to migrate tens of millions of PHP lines, is now building Skipper: a closed-loop coding agent designed to make AI-generated code verifiably correct, without human intervention.
Why do companies with the best intentions end up betraying their customers, employees, and mission? Eric Ries calls it “financial gravity” — an invisible force that pulls even the most principled companies toward corruption, and understanding it is the first step to resisting it.