Tech Lead Journal

Hosted by Henry Suryawirawan

Technology

Website RSS feed

Episodes

273

Latest episode

Jun 2026

Language

About the show

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. Hear from experienced technical leaders sharing their journey and philosophy for building great technical teams and achieving technical excellence. Find out what makes them great and how to apply those lessons to your work and team.

Listen to episodes

60 recent

June 15, 2026Episode 2611 hr 8 min

The Hidden Stories Sabotaging Your Culture Change

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.In this episode, Ronica Roth, author of “Practice Makes Culture” and co-founder of The Welcome Elephant, shares a practical framework for creating lasting organizational change. Drawing on 25 years of experience helping teams and companies transform, she explains why culture declarations and vision speeches alone never work — and what leaders at any level can do instead. Ronica introduces the concept of “welcoming elephants” — the emotional, systems, and room elephants that surface whenever change is attempted — and why acknowledging them is the first step toward real progress. She also unpacks why most culture lives beneath the surface, in hidden stories that employees carry without realizing it, and how those stories quietly undermine even well-designed initiatives.The conversation covers how to build psychological ownership so people invest in change rather than just comply with it, and why small, intentional daily practices — not grand overhauls — are what actually shift culture. The discussion also touches on applying these principles to AI transformation, where the emotional stakes are especially high and the hidden stories especially loud.Key topics discussed:Why 70% of change efforts fail — and what to do about itThe three types of “elephants” blocking organizational changeHidden stories: the invisible force sabotaging your cultureWhy declaring a new culture is necessary but not sufficientHow to create psychological ownership (not just buy-in)Using meetings as a daily practice for cultural changeLeading AI transformation with vulnerability and structureThe WOOP method for making personal behavior change stickTimestamps:(00:00:00) Trailer & Intro(00:02:43) Why Ronica Write a Book About IT Culture?(00:05:14) What Are the Three Types of Elephants That Hold Organizations Back?(00:11:05) Why Do 70% of Change Efforts Fail?(00:15:45) How Does Ronica Define the Different Layers of Culture?(00:20:57) Why Is Declaring a New Culture Necessary But Not Sufficient?(00:23:12) What Are the Three Pillars of Your Cultural Transformation Framework?(00:39:28) How Can You Turn Meetings Into a Daily Practice for Cultural Change?(00:48:51) How Can Leaders Address the Emotional Elephant of AI Transformation?(00:56:13) Can You Apply These Culture Change Principles to Personal Growth?(01:02:06) What Are the Five Culture Hacks for Scaling Cultural Impact?(01:04:49) 3 Tech Lead Wisdom_____Ronica Roth’s BioRonica Roth is a transformation expert dedicated to revolutionizing how organizations work. As cofounder of The Welcome Elephant consultancy, she helps leaders build thriving cultures where both business results and human potential flourish. With deep expertise in product management, business agility, and organizational change, Ronica brings a unique perspective shaped by her certification as a Leadership Circle® practitioner and her distinguished background as a Certified Scrum Trainer Emeritus. Her approach is informed by an MS in Journalism from Northwestern University and enriched by her earlier career in newspapers, giving her exceptional skills in storytelling and communication crucial for effective organizational change.Follow Ronica:LinkedIn – linkedin.com/in/ronicaroth Practice Makes Culture – itrevolution.com/product/practice-makes-cultureThe Welcome Elephant – thewelcomeelephant.coPractice Makes Culture Substack - practicemakesculture.substack.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/261.Follow @techleadjournal on LinkedIn and Instagram.Buy me a coffee or become a patron.

June 8, 2026Episode 2601 hr 18 min

Creator of Meta's Hack: Your AI Will Always Cheat — Here's How to Stop It

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.In this episode, Julien Verlaguet, creator of the Hack programming language at Meta and co-founder of SkipLabs, explains why AI agents will always try to cheat — gaming tests, quietly modifying logic while doing something else, and declaring work done when it isn’t. He draws on his experience migrating Meta’s PHP codebase to a statically typed system, drawing sharp parallels between convincing engineers to trust a new type checker and building systems that can trust an LLM. Julien makes the case for spec-driven development with validation layers at every step, where separate AI instances verify correctness and the code-writing agent is locked out of touching tests.He shares the story of an LLM that silently swapped a union for an intersection while splitting a file — a subtle bug that passed all tests — and why no human would ever have made that mistake. He then walks through how Skipper works: you write a spec, hand over control, and a compiler-like agent produces correct, runnable TypeScript without back-and-forth, backed by a sound incremental type system, reachability analysis, and a reactive runtime that applies diffs in milliseconds.He closes with a grounded take on how the developer role is shifting — not disappearing — toward the kind of design, integration, and oversight work that always mattered most.Key topics discussed:Why AI agents will always try to cheat on your testsThe union-vs-intersection bug an LLM introduced silentlySpec-driven development to keep LLMs on trackHow to separate the AI that verifies from the one that fixesSkipper: a compiler-like closed-loop coding agentSound, incremental TypeScript built for AI-speed iterationHot-reloading state without restarting — in millisecondsWhy developers are all becoming tech leadsTimestamps:(00:00:00) Trailer & Intro(00:02:34) How Did Julien Create the Hack Programming Language at Facebook?(00:05:53) Does Static Typing Make Your Code More Secure?(00:09:54) How Did You Convince Facebook Engineers to Adopt Hack at Scale?(00:17:15) How Can Engineers Overcome Skepticism Toward AI Coding Tools?(00:22:44) Should Junior Engineers Trust AI-Generated Code?(00:29:44) How Do You Build Reliable Guardrails for LLM-Generated Code?(00:42:15) What Validation Strategies Prevent AI Agents From Cheating on Tests?(00:45:54) What Is Skipper and How Does a Closed-Loop Coding Agent Work?(00:54:59) How Does Skipper Compare to Claude Code in Terms of Correctness?(00:58:27) How Do You Get Started With Skipper and What Does the Output Look Like?(01:04:50) How Will the Software Developer Role Change in an AI-First World?(01:09:06) 3 Tech Lead Wisdom_____Julien Verlaguet’s BioJulien Verlaguet is a programming language designer and the Founder and CEO of SkipLabs. He is best known as the creator of Hack—the gradually typed language he built at Facebook that currently powers over 100 million lines of the company’s production code. After creating the open-source reactive framework Skip, Julien founded SkipLabs in 2022. His company recently launched Skipper, a closed-loop coding agent that takes a single prompt from a developer and returns a running, validated service.Follow Julien:LinkedIn – linkedin.com/in/julien-verlaguet-b5710a20X – x.com/JulienVerlaguetSkipLabs - skiplabs.ioSkipper - skipperai.devSkipper’s Discord – discord.gg/bsnXyw2F9PLike this episode?Show notes & transcript: techleadjournal.dev/episodes/260.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

June 1, 2026Episode 2591 hr 0 min

Eric Ries: Why Good Tech Companies Go Bad, and How to Stop It

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.In this episode, Eric Ries, entrepreneur and author of The Lean Startup and Incorruptible, shares why building a great company isn’t just about having a strong vision — it’s about building structures that protect that vision from external pressure. Eric revisits the core ideas behind the Lean Startup and MVP, explaining how the purpose of a minimum viable product is not to ship fast but to learn fast. He then introduces the central thesis of his new book: that the corruption we see in companies isn’t caused by bad people, but by a financial system that pulls organizations away from their values. Drawing on stories of Sol Price, FedMart, Costco, HEB, Novo Nordisk, and Anthropic, he shows that incorruptible companies are built through a combination of ethos — a deep operational commitment to doing right — and structural governance that resists outside pressure. He also unpacks how false metrics like OKRs can hollow out a company’s integrity over time, and how Mary Parker Follett’s concept of the “invisible leader” helps culture survive beyond any single founder or CEO.Key topics discussed:What “financial gravity” is and why even good companies fall to itThe true purpose of an MVP (hint: it’s not about shipping fast)Why OKRs become dangerous false proxies over timeBlueprint for building a truly incorruptible companyWhy Costco and Novo Nordisk resisted forces that killed FedMartMary Parker Follett’s invisible leader explainedWhy Anthropic’s structure gives it a lasting competitive edgeHow everyday decisions become acts of systemic changeTimestamps:(00:00) Trailer & Intro(02:31) What Two Mega-Trends Make Lean Startup More Relevant Than Ever?(04:03) What Is the True Purpose of a Minimum Viable Product?(11:04) Has AI Actually Made Building Software Cheaper and Better?(13:41) What Two Stories Inspired the Book Incorruptible?(20:38) What Is Financial Gravity and Why Does It Corrupt Even Good Companies?(26:29) What Is Surrogation and Why Do OKRs Become Dangerous False Proxies?(29:55) What Is the Blueprint for Building an Incorruptible Company?(33:53) What Is the Invisible Leader and How Does It Keep Company Culture Alive?(39:56) What Governance Structures Can Shield a Company’s Mission from Financial Gravity?(48:27) Why Does Anthropic’s Unique Structure Give It a Competitive Advantage in AI?(51:43) 3 Tech Lead Wisdom_____Eric Ries’s BioOver the last two decades, Eric Ries’s ideas about continuous innovation, long-term thinking, governance, and market reform have reshaped company building and management practices. He is the creator of the Lean Startup method, and the author of the New York Times bestseller The Lean Startup; The Leader’s Guide; and The Startup Way.As a founder, he has put his own ideas into practice with The Long-Term Stock Exchange (LTSE); Answer.AI, an AI R&D lab; Virgil, a legal services startup; and IMVU. On The Eric Ries Show, he talks with world-class technologists, thought leaders, and executives building for the long-term. He lives in the San Francisco Bay Area with his wife and three children.Follow Eric:LinkedIn – linkedin.com/in/eriesX – x.com/ericriesPodcast – www.ericriesshow.comWebsite – incorruptible.coNewsletter – news.theleanstartup.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/259.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

May 18, 2026Episode 25859 min

Why Your AI Strategy Is Failing: The AI Paradox of Optimizing Coding Alone

What if faster coding is actually slowing your software delivery down? Most teams are pouring AI into the coding phase, but the real bottleneck is everywhere else.In this episode, Andrew Haschka, Field CTO at GitLab for Asia Pacific and Japan, explains why most AI strategies in software engineering are failing and what it takes to fix them. He introduces the AI paradox: teams invest heavily in AI-assisted coding, yet coding accounts for less than 20% of the software delivery lifecycle, leaving the biggest bottlenecks untouched.Andrew makes the case for intelligent orchestration — moving from isolated AI interactions to governed, end-to-end agentic flows that span planning, coding, testing, security, compliance, and release. He shares how a unified system of record forms the foundation for high-quality AI outcomes, and why fragmented tools and siloed context actively limit what AI can deliver. Drawing on real customer examples — including Ericsson’s 50% faster deployments and 130,000 hours saved in six months — he shows what a holistic approach actually looks like in practice.The conversation also covers how tech leads, developers, and junior engineers need to evolve their skills in a world where AI handles routine implementation. Andrew closes with a compelling argument: in the agentic era, governance isn’t just a compliance burden, it’s the primary source of competitive advantage.Timestamps:(02:30) What Are the Key Responsibilities of a Field CTO at GitLab?(03:26) Why Should Organizations Govern AI Strategy Rather Than Chase the Latest Features?(06:41) Why Is an End-to-End Agentic Flow More Valuable Than Individual AI Tools?(09:39) What Is the AI Paradox and How Does Intelligent Orchestration Solve It?(14:47) How Does Shifting Focus to Requirements Quality Transform Software Delivery Outcomes?(18:19) How Has GitLab Evolved Beyond CI/CD Into a Full End-to-End Delivery Platform?(20:20) What Should Software Teams Prioritize Beyond Coding in the AI Era?(24:14) How Do Organizational Silos Create a Capability Threshold for AI Adoption?(27:49) What Practical Strategies Can Organizations Use to Break Down Internal Silos?(30:58) How Did Ericsson Achieve 50% Faster Deployments and Save 130,000 Hours With GitLab?(33:07) How Should Software Developers Evolve in the Age of AI Agents?(36:26) How Is the Tech Lead Role Evolving in a Hybrid Human-AI Team?(39:22) How Can Junior Developers Keep Up With the Rapid Shift in Industry Expectations?(42:40) Why Do 79% of Singapore DevSecOps Practitioners Believe AI Will Create More Jobs?(45:27) Why Are Companies Reducing Staff Despite the Growing Demand for Software?(48:34) What Are the Most Common Pitfalls When Implementing Agentic Workflows?(52:29) What Practical Steps Should Engineering Leaders Take to Govern AI Responsibly?(55:13) Why Should Engineering Leaders Build an AI Strategy Before Choosing Technology?(57:15) 3 Tech Lead Wisdom_____Andrew Haschka’s BioAndrew Haschka serves as Field CTO for Asia Pacific & Japan at GitLab, where he acts as a trusted strategic advisor to enterprise customers and partners navigating complex technology transformation. With over 20 years of experience spanning software delivery, cybersecurity, cloud infrastructure, and organisational transformation, Andrew brings a rare combination of technical depth and executive-level counsel to the organisations he works with.Prior to GitLab, Andrew held senior leadership roles across APAC at Google and VMware, and has led large-scale digital transformation programmes for organisations including Downer, IBM, Jones Lang LaSalle, Thomson Reuters, Optus, and across the Fiji and Pacific Islands.Follow Andrew:LinkedIn – linkedin.com/in/andrewhaschkaLike this episode?Show notes & transcript: techleadjournal.dev/episodes/258.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

May 4, 2026Episode 2571 hr 15 min

The Future of Code Review: Stop Reviewing Line-by-Line, Start Governing AI Agents

(07:22) Brought to you by MailtrapMailtrap is a modern email delivery for developers with native SDKs support along with security compliant API & SMTP. Plus, you get 4,000 emails a month completely on their free tier! It also provides 24/7 support where you actually talk to real people, not an AI chatbot. Try Mailtrap for free at ⁠mailtrap.io⁠.What does code review mean when AI writes most of the code? The answer isn’t to review more carefully. It’s a fundamentally different process, one built around rules, agents, and governance rather than diffs and comments.In this episode, Itamar Friedman, founder and CEO of Qodo.ai, shares how AI is forcing a complete rethink of code review — from inline comments on code diffs to multi-agent governance systems that verify intent, architecture, and business logic at scale. He traces the evolution of code review through successive generations, explains why traditional static analysis is no longer sufficient, and lays out what a modern quality and governance layer actually looks like. Itamar also introduces the concept of “shift up” — extending quality checks into the planning phase so that technical product managers can contribute directly to shipping features — and explains how teams can move from vibe coding to viable, grounded development. The conversation also covers the race between AI labs, the role of open-source models, and a frank look at where the software developer role is heading by 2030.Key topics discussed:Why line-by-line code review doesn’t scale with AI-generated PRsThe generational evolution of code review tools (Gen 1 to 3.5)How multi-agent systems surface only what needs human attentionTurning tribal knowledge into enforceable rules and skillsShift-left and shift-up: embedding quality earlier in the workflowWhat the new agentic code review UI will look likeVibe coding vs. viable coding: the governance layer in betweenWhere the software developer role is headed by 2030Timestamps:(00:00:00) Trailer & Intro(00:02:50) How Has AI Driven the Evolution of Code Review to Multi-Agent Systems?(00:07:53) How Do We Move from Vibe Coding to Viable, Grounded Development?(00:12:35) Are Traditional Static Analysis Checks Still Sufficient in the AI Era?(00:16:27) How Do We Handle Exploding PR Volume Without Sacrificing Code Review Quality?(00:22:11) How Do We Evolve Code Review from Simple Comments to Senior-Level AI Reviews?(00:28:51) What Will the New Agentic Code Review UI Look Like?(00:33:32) How Does Qodo Differentiate Itself as an AI Code Review and Governance Platform?(00:37:15) What Do Shift-Left and Shift-Up Mean for the Future of Code Quality?(00:41:23) How Do We Maintain Quality When Running Multiple AI Agents in Parallel?(00:48:11) How Are Chinese AI Models Reshaping the Open-Source vs Closed-Source Race?(00:55:25) Which AI Models Excel at Code Review, and Are We Heading Toward Specialization?(01:03:16) Will Software Developers Still Be Needed as AI Automates More of Engineering?(01:08:50) 3 Tech Lead Wisdom_____Itamar Friedman’s BioItamar Friedman is the CEO and Co-Founder of Qodo, an AI code review platform used by 1M + developers. Before founding Qodo, Itamar was a founder of Visualead, which was acquired by the Alibaba Group. He then worked for Alibaba Group for 4 years as the Director of Machine Vision. Now, Itamar is dedicated to quality-first code generation.Follow Itamar:LinkedIn – linkedin.com/in/itamarfX (formerly Twitter) – @itamar_marQodo.ai – qodo.aiLike this episode?Show notes & transcript: techleadjournal.dev/episodes/257.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

April 27, 2026Episode 2561 hr 4 min

FeatureOps: The Safety Net You Need When Shipping with AI

(05:00) Brought to you by MailtrapMailtrap is a modern email delivery for developers with native SDKs support along with security compliant API & SMTP. Plus, you get 4,000 emails a month completely on their free tier! It also provides 24/7 support where you actually talk to real people, not an AI chatbot. Try Mailtrap for free at mailtrap.io.What happens when AI ships code faster than your team can review it? As agentic development accelerates your SDLC, the guardrails matter more than ever — and most teams don’t have them.In this episode, Egil Osthus, CEO of Unleash, makes the case for FeatureOps as a strategic capability — not just a developer convenience. He explains the shift from a project mindset to a product mindset, where releases are decoupled from deployments and business outcomes matter more than shipping scope. Egil breaks down the four pillars of FeatureOps — gradual rollout, full stack experimentation, surgical rollback, and lifecycle management — and why each one becomes even more critical as AI-generated code flows faster into production. He also warns against building your own feature flag solution in-house, and shares what the rise of agentic development means for engineers who must now act as guardians of an oversight layer.Key topics discussed:Project mindset vs. product mindset in software deliveryThe 4 pillars of FeatureOps and what each one solvesWhy feature flags scare executives — and how to win them overDecoupling deployment from release across Dev, PM, and MarketingThe danger of rolling your own feature flag solutionHow local evaluation keeps feature flags fast and privateBlast radius management in an AI-accelerated SDLCWhat vibe coders get wrong about day-two operationsTimestamps:(00:00) Trailer & Intro(02:36) What Is the Current State of Feature Flag Adoption Across the Industry?(05:32) Why Is Feature Flag Adoption So Challenging Despite Its Apparent Simplicity?(10:44) How Does FeatureOps Differ From CI/CD and Progressive Delivery?(12:26) What Are the Four Core Pillars of FeatureOps?(16:11) How Can Teams Shift the Perception of Feature Flags From Tactical to Strategic?(20:46) How Do Feature Flags Align the Needs of Developers, Product Managers, and Marketing?(25:09) How Do Organizations Effectively Define Responsibilities for Strategic Feature Flags?(28:03) Does Using Feature Flags Enable Your Team to Deploy on Fridays?(30:41) What Is Unleash and How Does It Scale for Enterprise Needs?(34:54) What Are the Hidden Dangers of Building Your Own Feature Flag Solution?(39:32) Why Are Local Evaluation and Privacy Core to Unleash’s Design?(44:48) How Does the Rise of AI Impact the Evolution of FeatureOps?(52:02) What Specific Guardrails Does FeatureOps Provide to Improve Safety?(54:21) Can FeatureOps Platforms Use AI to Autonomously Manage Feature Rollouts?(55:33) What Essential FeatureOps Advice Should Every Vibe Coder Follow?(59:53) 3 Tech Lead Wisdom_____Egil Osthus’s BioEgil Østhus is the co-founder and CEO of Unleash, the world’s leading open-source feature management platform. As a seasoned enterprise technologist and product strategist, he operates at the cutting edge of business and software engineering.Egil’s mission is to help technology leaders and businesses move beyond traditional DevOps by embracing FeatureOps, a new methodology that provides a critical safety net for the accelerating, and often risky, world of agentic software development. He has a unique ability to speak the language of both engineers and senior executives, making complex topics accessible and actionable.Follow Egil:LinkedIn – linkedin.com/in/egilconrUnleash – getunleash.ioLike this episode?Show notes & transcript: techleadjournal.dev/episodes/256.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

April 20, 2026Episode 2551 hr 16 min

Stop Vibe Coding: Spec-Driven Development with The BMad Method

What if vibe coding is the worst thing you could do with AI agents? The developers seeing the biggest gains aren’t prompting harder. They’re planning smarter, spec-first, and treating AI as a facilitator rather than a code generation engine.In this episode, Brian Madison, creator of the BMad Method, shares how a year of late-night AI experiments led him to a structured, Agile-inspired approach to building software with AI agents. Brian explains why jumping straight into agent mode without upfront planning (what most people call vibe coding) reliably hits a wall, and how a disciplined spec-first workflow breaks through that ceiling.He walks through the BMad Method’s core workflow: brainstorming, PRD, architecture, UX design, and context-rich user stories, each feeding into the next so the agent always has exactly what it needs. Brian also recounts a transformative two-week sprint he ran with his team where engineers were given permission to fail, and how that single experiment changed the way his entire organisation works with AI.Finally, he reflects on what this shift means for the future of software engineering — where the unit of work is moving from tasks and stories to full features and epics, and every engineer can operate more like a tech lead.Key topics discussed:Why vibe coding hits a wall and how spec-driven dev fixes itUsing AI as a facilitator, not just a code generatorThe BMad Method: PRD → architecture → context-rich storiesHow a 2-week “no typing” sprint transformed his engineering teamGiving teams permission to fail as a leadership toolThe shift from user stories to epics as the unit of workWhy problem decomposition is engineers’ biggest AI superpowerTimestamps:(00:00:00) Trailer & Intro(00:02:44) How Did the US Army Shape Brian’s Journey into Software Engineering?(00:06:35) How Can Engineers Overcome Imposter Syndrome and Build Self-Confidence?(00:10:23) What Does BMad Actually Stand For?(00:13:49) What Is the BMad Method?(00:22:11) How Does BMad Approach Context and Spec Engineering?(00:29:02) What Sparked the Creation of the BMad Method?(00:44:55) What Productivity Gains Has the BMad Method Produced?(00:48:36) How Will AI Change the Unit of Work for Software Engineers?(00:55:51) How Does BMad Keep Specs and Code in Sync Over Time?(01:01:01) What Is the Best Way to Get Started with the BMad Workflow?(01:05:00) Which AI Models and Tools Does the BMad Method Support?(01:08:21) 4 Tech Lead Wisdom_____Brian Madison’s BioBrian Madison is the creator of the BMad Method, an open-source framework that treats AI as a facilitator for workflows across any domain—software development, product management, operations, and beyond. Used globally, the BMad Method helps people work through complex processes using AI personas, from engineers driving spec-driven development to product managers crafting better PRDs and requirements.Currently a Senior Engineering Manager at Extend, Brian led product engineering teams toward becoming an AI-native organization and now leads the entire AI SDLC transformation for the company, using the BMad Method as a framework, reimagining how AI flows through the full software development lifecycle.Brian’s approach to leadership was forged during his service in the U.S. Army, where he learned the values of servant leadership, discipline, and mission-first execution.Follow Brian:LinkedIn – linkedin.com/in/bmadcodeBMadWebsite – bmadcode.comDocs – docs.bmad-method.orgGitHub – github.com/bmad-code-org/BMAD-METHODDiscord – discord.gg/gk8jAdXWmjYouTube – youtube.com/@BMadCodeX – x.com/BMadCodeFacebook – facebook.com/@BMadCodeLike this episode?Show notes & transcript: techleadjournal.dev/episodes/255.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

April 13, 2026Episode 2541 hr 3 min

Why Incumbents Will Fall: How to Build a Hyperadaptive AI-Native Organization

Why do 80-95% of AI initiatives fail — and why is your organization’s structure to blame? Most companies are treating AI like a software upgrade, when it actually demands a complete rewiring of how work gets done.In this episode, Melissa Reeve, author of Hyperadaptive and organizational change expert, shares a practical model for transforming legacy enterprises into AI-native organizations built to thrive — not just survive — in the age of AI. Drawing on her experience with the Toyota Production System, Scaled Agile, and deep research into leading AI adopters, Melissa argues that the real barriers to AI adoption are structural: Taylorist hierarchies, functional silos, and decision bottlenecks that organizations have never been forced to dismantle — until now. She introduces the Hyperadaptive model, a five-stage maturity path that gradually rewires how organizations operate, from establishing AI governance and identifying champions, to deploying agentic AI and organizing around customer value streams. Unlike past transformations, AI will compress both the strategy-to-execution and concept-to-delivery dimensions simultaneously — and the organizations that fail to adapt will be displaced by AI-native competitors rising far faster than Uber or Airbnb ever did.Timestamps:(00:00:00) Trailer & Intro(00:02:50) How Did Melissa’s Background in Lean and Agile Lead to the Hyperadaptive Model?(00:05:57) How Is the AI Revolution Different From Past Digital Transformations?(00:07:39) Will AI-Native Companies Disrupt Incumbents the Way Airbnb and Uber Did?(00:09:08) How Did the DevOps Model Inspire the Concept of Automated Execution Pipelines?(00:12:41) What Is a Hyperadaptive Organization?(00:14:10) Why Has AI Adoption Failed to Deliver Results in Most Organizations?(00:17:05) What Are the Three Structural Barriers to AI Adoption?(00:19:39) Why Is Taylorism Considered a Major Barrier to Becoming Hyperadaptive?(00:22:48) What Are the Five Capabilities Required to Become Hyperadaptive?(00:26:45) Why Does AI Make Age-Old Principles Like Lean and Agile More Relevant Than Ever?(00:28:49) How Will the Human-in-the-Loop Role Evolve as Agentic AI Takes Over?(00:32:52) How Should Organizations Start Transitioning from Functional Silos to Value Streams?(00:35:07) How Is AI Enabling Adjacent Competencies and Expanding Professional Roles?(00:38:43) Will AI Replace Workers or Unlock More of What Organizations Can Achieve?(00:41:52) What Are the Five Stages of Maturity for Becoming Hyperadaptive?(00:48:21) Why Do Most AI Implementations Fail When Organizations Skip the Foundation?(00:50:55) What Does Dynamic AI Governance Look Like in Practice?(00:55:20) How Does Kahneman’s Thinking Fast and Slow Explain the Human-AI Partnership?(00:58:07) How Can AI Help Organizations Optimize for People, Profit, and Planet?(01:00:24) 3 Tech Lead Wisdom_____Melissa Reeve’s BioMelissa Reeve creator of the Hyperadaptive Model and author of Hyperdaptive: Re-wiring the Enterprise to Become AI-Native. Hyperadaptive brings together process excellence, systems thinking, and the human side of AI integration to help leaders reimagine how their organizations learn and adapt.Prior to leaning into AI, Melissa spent 25 years as an executive and Agile thought leader, which led to pioneering work in Agile marketing and her role as the first VP of Marketing at Scaled Agile and co-founding the Agile Marketing Alliance. She lives in Boulder, CO, with her husband, dogs, and chickens, where she enjoys hiking and gardening.Follow Melissa:LinkedIn – linkedin.com/in/melissamreeveWebsite – hyperadaptive.solutionsSubstack - https://intel.hyperadaptive.solutions/ Hyperadaptive - https://hyperadaptive.solutions/bookLike this episode?Show notes & transcript: techleadjournal.dev/episodes/254.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

April 6, 2026Episode 2531 hr 29 min

How Vidio (Indonesia's #1 Streaming Platform) Built Great Engineering Culture — Now Supercharged by AI

What does it take to build a world-class engineering culture when you start with five engineers on minimum wage? Tommy Sullivan did exactly that at Vidio — and the team’s average tenure of seven years tells you everything about whether it worked.In this episode, Tommy Sullivan, CTO of Vidio (Indonesia’s largest streaming platform) shares how he built an engineering culture from almost nothing, growing a team of five to over two hundred using Extreme Programming principles and a relentless focus on hiring for attitude over aptitude. Tommy traces his journey from Pivotal Labs in San Francisco to the early days of Indonesia’s tech boom, explaining why Vidio survived when well-funded competitors like Hooq and iFlix all shut down.Along the way, he gets into where AI has worked and where it has failed at Vidio, how the team is rethinking pair programming in the age of AI agents, what it takes to stream four terabytes per second during live events, and why protecting code quality is ultimately a culture problem, not a tooling one. Tommy also shares a hard-earned view on the agentic AI trend and why understanding the underlying mechanics matters more than chasing the hype.Key topics discussed:How Extreme Programming built Vidio’s 7-year average tenureHiring for attitude: why aptitude alone isn’t enoughPair programming reimagined for the AI-agent eraWhy code quality is a culture problem, not a tool problemAI failures and wins at VidioHow Vidio streams 4TB/s to 2.2M concurrent usersAVOD vs. SVOD: the model that saved VidioVendor independence for CDN and AI — why it mattersWhat engineers need to understand about agentic AITimestamps:(00:00:00) Trailer & Intro(00:03:07) How Did Tommy Go From Silicon Valley to Jakarta?(00:07:22) How Has Indonesia’s Tech Scene Evolved Over the Past Decade?(00:13:12) What Happened to Indonesia’s Engineering Talent After the VC Bubble Burst?(00:15:03) Why Is Indonesia One of the World’s Most Exciting Tech Markets?(00:17:26) How Do You Build a World-Class Engineering Team When Starting From Scratch?(00:22:01) What Are the Hidden Benefits of Pair Programming Beyond Code Quality?(00:25:28) How Is AI Blurring the Lines Between Engineers and Product Managers?(00:28:48) How Do You Justify XP Practices to a Results-Driven Business?(00:36:11) What Has Worked and What Has Failed When Integrating AI at Vidio?(00:44:19) Is AI an Amplifier or a Threat to Software Engineers?(00:46:59) How Does Vidio Use Team Rotation and Shared Ownership to Retain Engineers?(00:51:16) How Do You Protect Code Quality Culture in the Age of AI?(00:54:16) What Metrics Actually Matter for Engineering Quality?(00:58:07) How Will AI-Generated Content Reshape the Streaming Industry?(01:06:51) What Does It Take to Stream at 4 Terabytes per Second?(01:09:26) How Do You Keep a Streaming Platform Stable During Massive Live Events?(01:14:12) How Did Vidio Survive When Other OTT Platforms Failed?(01:18:15) Why Does Vendor Independence Matter for Both CDNs and AI?(01:21:44) What Should Engineers Understand About the Agentic AI Trend?(01:26:17) Tech Lead Wisdom_____Tommy Sullivan’s BioTommy Sullivan leads the software engineering behind Vidio — Indonesia’s leading video-streaming platform. Before joining the Vidio / Emtek group, he helped startups and global enterprises implement agile engineering and lean product development practices in Silicon Valley and Southeast Asia. As a founding member of Vidio, Tommy shaped its early development and steered its evolution from a user-generated content platform to a premium streaming service supporting millions of subscribers. He leads with a focus on data-driven decisions and a humble, collaborative developer culture.Follow Tommy:LinkedIn – linkedin.com/in/tommybsullivanLike this episode?Show notes & transcript: techleadjournal.dev/episodes/253.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

March 30, 2026Episode 2521 hr 4 min

Why Senior Engineers Struggle as Tech Leads: The 3 Mindset Shifts That Fix It

Why do so many talented senior engineers struggle the moment they step into a tech lead role? Most of them are promoted based on their coding ability, but that same strength becomes a liability the moment they start leading a team.In this episode, Anemari Fiser, tech lead coach and author of “Leveling Up as a Tech Lead”, shares the three mindset shifts that define the transition from senior engineer to effective tech lead: moving from an “I” to a “We” mindset, shifting focus from code to value, and trading short-term thinking for long-term impact. She explains why so many engineers hold on to coding out of fear, how to delegate without losing accountability, and why most technical problems are really people problems in disguise. Anemari also addresses how AI is reshaping the tech lead role and why the fundamentals of leadership still apply regardless of the tools your team uses.Key topics discussed:The 3 mindset shifts required for the transition to tech leadWhy your coding strength can hold back your teamHow to let go of coding without losing your technical edgeDelegation secrets: setting expectations that actually stickInfluencing without authority — and when it’s not enoughHow to measure your impact when results are hard to seeLeading your team through AI adoption without creating chaosTimestamps:(00:00:00) Trailer & Intro(00:02:41) What Motivated Anemari to Write Her Book, Leveling Up as a Tech Lead?(00:05:41) How Is the Tech Lead Role Defined?(00:06:45) How Does the Engineering Manager Role Differ From a Tech Lead?(00:09:37) Why Is the Transition to Tech Lead One of the Most Challenging Career Moves?(00:14:21) How Can Tech Leads Shift From Short-Term to Long-Term Thinking?(00:18:34) How Can Tech Leads Learn to Let Go of Writing Code?(00:26:30) Why Is Every Tech Problem Actually a People Problem?(00:30:52) How Can Tech Leads Delegate Effectively?(00:37:18) How Can Tech Leads Influence Without Authority?(00:40:37) Why Is Accountability Without Authority Unfair to Tech Leads?(00:43:42) How Can Tech Leads Measure Their Impact?(00:46:52) How Does AI Change the Role of a Tech Lead?(00:52:26) Should Tech Leads Use AI to Get Back to Hands-On Development?(00:55:33) How Can Tech Leads Stay Accountable for AI-Generated Code?(01:00:26) With AI in the Mix, Is a Tech Problem Still Just a People Problem?(01:01:10) 3 Tech Lead Wisdom_____Anemari Fiser’s BioAnemari Fiser is a tech leadership trainer, coach and O’Reilly author of Leveling Up as a Tech Lead. With over a decade in tech, she has coached 500+ engineers and trained 400+ tech leads worldwide, and shares practical leadership insights on LinkedIn with a community of 30,000+ tech professionals.Follow Anemari:LinkedIn – linkedin.com/in/anemari-fiserWebsite – anemarifiser.com Leveling Up as a Tech Lead – oreilly.com/library/view/leveling-up-as/9781098177508Like this episode?Show notes & transcript: techleadjournal.dev/episodes/252.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.