Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Tech Lead Journal

Tech Lead Journal artwork

Don't Outsource Your Thinking: How to Lead in the AI-Native Era - Emilie Schario

Sep 7, 202659 minAudio
ShareXLinkedInFacebookWhatsAppEmail

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. She explains why Kilo went all-in on being model agnostic, supporting over 500 models instead of betting on a single lab. Emilie shares her core rule for using AI responsibly: never outsource your thinking, especially when it comes to auth, billing, or security. She introduces a metric more companies should be tracking, spend per merged pull request, as a better signal of value than raw AI cost. Emilie also talks about the “killing problem” that comes with software becoming nearly free to ship, and why teams now discover product-market fit after shipping rather than before. She closes with how engineers are shifting from producers to reviewers, and what that means for anyone now managing a team of AI agents instead of just their own code. Key topics discussed: Why Kilo Code refuses to bet on a single AI model The one rule for not losing control to AI agents A better way to measure AI spend: cost per merged PR Why shipping software is nearly free, and why that’s risky How AI-native teams find product-market fit after shipping Why senior engineers adapt to AI agents the fastest Building a council of reviewers for high-risk code changes What the Anaconda acquisition means for Kilo Code Timestamps: (00:00) Trailer & Intro (02:27) What Is Kilo Code All About? (03:31) How Do You Avoid Getting Overwhelmed by 500 Plus AI Models? (04:34) How Does a Multi-Platform Approach Benefit Developers? (07:19) How Does Kilo’s Agent Harness Differ From Other Tools? (09:51) Why Will Model Choice Matter Less Over Time? (11:20) What Tools Help You Pick the Right Model for Each Task? (14:16) What Does the Anaconda Acquisition Mean for Kilo Code? (15:43) Why Should You Measure AI Spend Per Merged Pull Request? (18:54) How Do You Balance Speed and Control in AI Development? (20:28) Why Should Companies Treat AI as Operational Infrastructure? (23:31) How Do AI-Native Organizations Run Their Day-to-Day Workflows? (27:58) How Will High-Performing AI Organizations Differentiate Themselves in the Future? (30:11) What Is the “Killing Problem” Now That Shipping Software Is Free? (32:40) How Do You Shift to a Metrics-First Mindset? (34:24) How Is the Product Manager’s Role Changing in AI-Native Teams? (37:06) How Do You Balance Rapid Feature Delivery With Product Quality? (41:48) How Is the Software Engineer’s Role Evolving in the Age of AI? (43:57) What Is the Best Advice for Junior Engineers Entering an AI-Native World? (45:51) How Can Developers Handle the Cognitive Load of Code Reviews? (49:11) How Should Docs and Code Attribution Evolve With AI Agents? (53:06) How Can AI Improve Your Life Outside of Work? (55:04) 3 Tech Lead Wisdom _____ Emilie Schario’s Bio Emilie is VP, Engineering at Anaconda and the former cofounder of Kilo (acquired by Anaconda), where she focuses on turning AI investment into real engineering output. She operates at the intersection of AI tooling, engineering org design, and the day-to-day realities of running high-performing teams, helping organizations translate innovation into measurable impact. Follow Emilie: LinkedIn - linkedin.com/in/emilieschario Playbooks and Priority newsletter - emilie.substack.com Kilo Code - kilo.ai/ Like this episode? Show notes & transcript: techleadjournal.dev/episodes/268. Follow @techleadjournal on LinkedIn and Instagram. Buy me a coffee or become a patron.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. AI-Native Is a Journey: From Coding Agents to Software Factories - Vinay Perneti

    Nov 16, 20261 hr 1 minAudio

    What does it really take for an engineering team to become AI-native? Vinay explains why AI-native is a journey rather than a destination, and how engineering leaders can keep their teams ahead as models improve. In...

    Credit the people on this episode

  2. How to Build a Successful Product: Stop Chasing Pain Points, Start Finding PULL - Rob Snyder

    Oct 26, 202653 minAudio

    Why do startups with great customer research, design partners and real traction still fail to sell? Rob did everything the playbook says, then spent two years unable to close a sale. He explains what the playbook gets...

    Credit the people on this episode

  3. Stop Being the Hero: How Developers Become Great Software Architects - Lee Atchison

    Oct 12, 20261 hr 2 minAudio

    Why do the best developers often make the worst software architects? The skills that make someone a hero developer can become the habits that hold their team back once they move into architecture. In this episode, Lee...

    Credit the people on this episode

  4. The IT/OT Handbook: From Silos to Sustainable Digitalization - David Ariens & Willem van Lammeren

    Sep 28, 20261 hr 7 minAudio

    Why can’t you “move fast and break things” in a factory? Because a small software bug doesn’t just crash an app, it can shut down a plant the size of a small city. David and Willem explain the hidden world of...

    Credit the people on this episode

  5. The Father of AI Assistant on Why Joy Comes Before Success - Kevin Surace

    Aug 24, 202656 minAudio

    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...

    Credit the people on this episode