Tech Lead Journal

• #231 - Faster Code Reviews, Faster Code Shipping with Stacked PRs - Greg Foster

  Are long code review cycles killing your engineering team’s velocity? Learn how top engineering teams are shipping code faster without sacrificing quality.In this episode, Greg Foster, CTO and co-founder of Graphite, discusses the evolution of code review practices, from the fundamentals of pull requests to the future of AI in code review workflows. He shares the secrets behind how the Graphite team became one of the most productive engineering teams by leveraging techniques like small code changes and stacked PRs (pull requests).Key topics discussed:The evolution of code review from bug-hunting to knowledge sharingBest practices for PRs and why small PRs get better feedbackHow stacked PRs eliminate waiting time in development workflowsThe rise of AI in the code review processWhy AI code review works best as an automated CI checkHow Graphite achieves P99 engineering productivityHiring engineers in the age of AI-assisted codingTimestamps:(00:00) Trailer & Intro(02:21) Career Turning Points(05:11) Now is The Golden Time to Be in Software Engineering(09:08) The Evolution of Code Review in Software Development(14:59) The Popularity of Pull Request Workflow(21:01) Pull Request Best Practices(26:17) The Stacked PR and Its Benefits(34:07) How Graphite Ships Code Remarkably Fast(40:03) The Cool Things About AI Code Review(45:23) Graphite’s Unique Recipes for Engineering Productivity(50:55) Hiring Engineers in the Age of AI(55:31) 2 Tech Lead Wisdom_____Greg Foster’s BioGreg Foster is the CTO and co-founder of Graphite, an a16z and Anthropic-backed company helping teams like Snowflake, Figma, and Perplexity ship faster and scale AI-generated code with confidence. Prior to Graphite, Greg was a dev tools engineer at Airbnb. There, he experienced the impact of robust internal tooling on developer velocity and co-founded Graphite to bring powerful, AI-powered code review to every team. Greg holds a BS in Computer Science from Harvard University.Follow Greg:LinkedIn – linkedin.com/in/gregmfosterX – x.com/gregmfosterEmail – [email protected] – graphite.devGraphite X – x.com/withgraphiteLike this episode?Show notes & transcript: techleadjournal.dev/episodes/231.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

  --------  

  1:00:57

  --------

  1:00:57
• #230 - Technical Coaching in the Age of AI with Samman (Ensemble) - Emily Bache

  Struggling with technical debt and code quality? Learn how a technical coach can help your team level up.In this episode, Emily Bache, a Samman technical coach, shares her proven method for building better engineering teams through structured learning and collaborative coding. We explore ensemble programming, learning hours, and why AI makes fundamental engineering practices more important than ever.Key topics discussed:The role of a Technical Coach and the Samman Method explainedHow AI amplifies good engineering practices instead of replacing themHow to use ensemble programming to achieve single-piece flowRunning effective ensemble sessions and avoiding common failure modesWhy learning is part of the work, not only a side activityWhy pull requests should not be the primary tool for mentoring junior developersThe dangerous trend of “vibe coding” with AI toolsTimestamps:(00:00) Trailer & Intro(02:22) Career Turning Points(03:23) Being Part of Modern Engineering YouTube Channel(04:27) The Role of a Technical Coach(05:42) The Impact of AI on Technical Coaching(08:20) Sofware Engineering is a Learning Process(09:55) Optimizing Learning With Samman Method(11:40) The Samman Method: Ensemble (Mob Programming)(14:59) The Main Benefit of Ensemble: Single Piece Flow(17:26) How to Do Ensemble and Avoid Common Failure Modes(20:27) The Types of Coding to Ensemble On(22:12) The Importance of Trust, Communication, and Kindness(23:52) Common Things Development Teams Are Struggling With(25:37) Prompt Engineering(27:16) The Samman Method: Learning Hours(29:08) Learning is Part of the Work(31:32) The Practice of Learning as a Team(34:39) The Constraint When Learning from Pull Requests(36:30) Putting Aside Time for Learning Hours(39:14) Becoming a Technical Coach(41:23) How to Measure the Effectiveness of Technical Coaching(43:52) Danger of AI Assisted Coding(46:59) The (Still) Important Skills in the AI Era(49:56) Why We Should Not Refactor Through AI(52:41) The Samman Method & Technical Coaching Resources(53:29) 3 Tech Lead Wisdom(54:56) Finding Mentors for Career Progression_____Emily Bache’s BioEmily Bache is an independent consultant, YouTuber and Technical Coach. She works with developers, training and coaching effective agile practices like Refactoring and Test-Driven Development.Emily has worked with software development for 25 years, written two books and teaches courses on platforms including Pluralsight and O’Reilly. A frequent conference speaker, Emily has been invited to keynote at prestigious developer events including EuroPython, Craft and ACCU. Emily founded the Samman Technical Coaching Society in order to promote technical excellence and support coaches everywhere.Follow Emily:LinkedIn – linkedin.com/in/emilybacheX – x.com/emilybacheMastodon – sw-development-is.social/web/@emilybacheGitHub – github.com/emilybacheWebsite – emilybache.comSamman Coaching – sammancoaching.orgYouTube – youtube.com/@EmilyBache-tech-coachModern Software Engineering – youtube.com/@ModernSoftwareEngineeringYTLike this episode?Show notes & transcript: techleadjournal.dev/episodes/230.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

  --------  

  57:25

  --------

  57:25
• #229 - The Management System for High-Performing Engineering Organizations - Michi Kono

  Why do engineering teams slow down as they scale? It’s not the technology—it’s the management systems.In this episode, Michi Kono, CTO at Garner Health and former engineering leader at Meta, Capital One, and Stripe, shares his battle-tested approach to building scalable engineering organizations. We explore why most teams slow down as they scale and how to build systems that accelerate growth. Our conversation covers everything from designing effective org charts to creating accountability without killing psychological safety. You’ll learn practical strategies for nurturing engineering culture while maintaining high-performance standards.Key topics discussed:The challenges of hypergrowth and the need to constantly reinvent yourselfHow to avoid slowdowns by holding teams accountable for outcomes, not just shipping codeThe art of designing org charts that maximize team autonomyBuilding a culture of accountability and learning from mistakes without blameWhen managers should stop writing code (and why this decision matters)The difference between being a people manager and an executiveWhy communication becomes the most critical skill at senior levelsTimestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(03:55) Skills Advice for Engineers(06:46) The Challenges of a Hypergrowth Company(09:09) Learning and Growing in a Hypergrowth Company(12:07) The Slowdown in Engineering as You Scale(15:55) Designing Organization Structure Well(18:11) Effective Organization Chart Tips(21:05) Nurturing a Good Engineering Culture(25:37) Nurturing Psychological Safety(28:14) Learning from Mistakes & Performance Review(30:27) Being a Mission-Driven Company(32:11) Aligning Mission and Values in the Day-to-Day Work(34:45) The Importance of Management System in Organization(41:53) The Importance of Having Good Managers(45:30) For Strong ICs: Writing Code or Being a Manager?(50:55) The Difference Between a Manager Role and Executive Role(56:01) A Unique Thing Learned from Doing Payment Systems(58:43) 3 Tech Lead Wisdom_____Michi Kono’s BioMichi Kono is the Chief Technology Officer (CTO) at Garner Health, a company on a mission to help people get better healthcare. With a unique and extensive career spanning multiple industries, Michi has navigated the entire spectrum of the tech world. He began his journey in startups, one of which was acquired, leading him to a role at Capital One. From there, he gained invaluable experience at tech giants like Meta and financial-tech leader Stripe before taking the helm at Garner Health. Michi is passionate about the art and science of scaling engineering teams, building resilient cultures, and designing effective management systems to drive success in high-growth environments. He believes deeply in empowering engineers, fostering accountability, and the critical importance of clear communication for any leader.Follow Michi:LinkedIn – linkedin.com/in/michikonoTwitter – x.com/michikonoGarner Health – getgarner.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/229.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

  --------  

  1:01:04

  --------

  1:01:04
• #228 - Leading Transformational Engineering Teams with Craft in the AI Era - Mohan Krishnan

  How do you build a high-performing engineering team in the AI era? And will AI make fundamental engineering skills obsolete?In this episode, Mohan Krishnan, Head of Engineering at Grab, shares lessons from leading multiple transformational engineering teams. Drawing from his experience at Grab, Bukalapak, BBM Emtek, and Pivotal Labs, Mohan explains why core engineering fundamentals still matter, even in the age of AI, and will become even more valuable than ever. He discusses building disciplined, high-performing engineering teams and the importance of hands-on leadership. We also explore the unique challenges and vast potential of the tech landscape in Southeast Asia.Key topics discussed:Why foundational skills like TDD and system design are becoming more critical in the age of generative AIHow to effectively use AI as a pair programmer for upskilling and idea generation, while avoiding the pitfalls of “vibe coding”Mohan’s “sports team” analogy for building successful engineering teams with discipline, a mix of seniority, and a culture of deep learningThe importance of hands-on technical leadership, and why even CTOs should “dive deep” to set the right engineering barThe state of engineering talent in Southeast Asia and what’s needed to bridge the gap in deep tech and AI developmentActionable career advice for junior and mid-career professionals navigating the AI-infused software industryTimestamps:(00:00:00) Trailer & Intro(00:02:08) Career Turning Points(00:06:03) Things We Should Learn in the AI Era(00:09:53) AI as a Pair Programmer(00:13:58) The Danger of Outsourcing Our Thinking to AI(00:17:29) The Dopamine Hit of Using AI(00:20:36) Building a Successful Transformational Engineering Team(00:25:33) The Discipline Rigor in An Engineering Team(00:29:14) Understanding & Delivering Outcomes for the Business(00:32:21) Having a Tough Approach as an Engineering Leader(00:39:07) Going Back as an IC at Google(00:45:40) The Importance of Being Hands-On with Recent Technologies for Leaders(00:52:40) Hands-on vs Micromanagement(00:55:11) Engineering Talents in Southeast Asia(00:58:06) Building Tech Talents in Southeast Asia(01:01:17) Bridging the AI Gap in Southeast Asia(01:04:03) Should We Still Pursue a Tech Career in the AI Era?(01:07:24) 2 Tech Lead Wisdom_____Mohan Krishnan’s BioMohan Krishnan, based in Singapore, is currently a Head of Engineering at Grab. Mohan Krishnan brings experience from previous roles at Google, Bukalapak, BBM and Pt. Kreatif Media Karya. Mohan Krishnan holds a 1998 - 2002 Bachelor of Engineering in Multimedia, Electronics at Multimedia University. With a robust skill set that includes Ruby on Rails, Multithreading, Web Services, HTML, Services and more.Follow Mohan:LinkedIn – linkedin.com/in/mohangkLike this episode?Show notes & transcript: techleadjournal.dev/episodes/228.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

  --------  

  1:09:57

  --------

  1:09:57
• #227 - Infrastructure as Code: Delivering Dynamic Systems for the Cloud Age - Kief Morris

  How has Infrastructure as Code changed in the last five years? Explore the key shifts and how to align your infrastructure to real business value.In this episode, Kief Morris, a Distinguished Infrastructure Engineer at Thoughtworks, returns to discuss the third edition of his book “Infrastructure as Code.” He shares fresh insights on designing and delivering dynamic systems for today’s cloud-driven world. Kief explores the evolution of IaC, practical methods for modern teams, the next generation of tools, and lessons learned from the recent years. Learn how to align infrastructure with business needs and manage today’s growing infrastructure complexities.Key topics discussed:How “Infrastructure as Code” book has evolved across three editionsWhy infrastructure decisions must align with business valueHow IaC and the toolchain have evolved over the last few yearsHandling the growing complexity of modern infrastructureThe rise of platform engineering and internal developer platformsTerraform vs. OpenTofu: which one should you use?Balancing governance, speed, and innovation in the cloud eraThe current limitations and role of AI in managing infrastructureTimestamps:(00:00) Trailer & Intro(02:39) Updates in the Last Five Years(04:13) Infrastructure as Code Definition(05:58) The Practice of Infrastructure as Code(06:32) The Differences Between the Book Editions(10:21) Aligning Infrastructure to the Business Value(15:03) Handling the Growing Infrastructure Complexities(19:10) The Tools and New Inventions in IAC(24:11) Terraform vs OpenTofu(27:38) Orchestrating Infrastructure Changes Using IAC(30:35) Platform Engineering(33:06) Internal Developer Platform Key Success Factor(37:15) Key Considerations of Building Teams with Infrastructure Skills(41:56) Infrastructure Compliance and Governance(45:53) Using AI for Infrastructure as Code(50:31) Using AI for Troubleshooting and Root Cause Analysis(51:50) 3 Tech Lead Wisdom_____Kief Morris’s BioKief Morris is the author of the O’Reilly book Infrastructure as Code, and is a Distinguished Infrastructure Engineer at Thoughtworks, based in London. He works with clients and project teams around the world to explore, shape, and share better ways of working with cloud and infrastructure architecture.Kief started out as a developer and systems administrator in the dot-com boom days, then worked with a series of digital scaleups applying infrastructure automation before DevOps was a thing. He joined Thoughtworks in 2010 as the wider industry was discovering Infrastructure as Code, DevOps, and Cloud, which gave him the opportunity to bring what he had learned in the previous fifteen years to enterprise clients in many industries and many countries.He wrote the book Infrastructure as Code (now on the third edition) to share these ideas with a wider audience, which has given him a platform to meet and learn from an ever-growing variety of people and organizations.Follow Kief:LinkedIn – linkedin.com/in/kiefmorrisTwitter – x.com/kiefBlueSky – bsky.app/profile/kief.comPersonal Website – kief.comInfra as Code Website – infrastructure-as-code.com Infrastructure as Code – https://www.oreilly.com/library/view/infrastructure-as-code/9781098150341/Like this episode?Show notes & transcript: techleadjournal.dev/episodes/227.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

  --------  

  56:11

  --------

  56:11

More Technology podcasts

Trending Technology podcasts

About Tech Lead Journal