AI can scaffold an app in seconds, but can it refactor that thousand-line React file when the first bug hits production?
In this episode, I sit down with Brian Jenney software engineer and program owner of the coding bootcamp Parsity, to draw a hard line between “code that runs” and “code that lasts.” From mentoring career-switchers to stress-testing AI in real-world pipelines, Brian shares why craftsmanship and product judgment still beat copy-paste prompts.
🔗 Essential Links (Start Here!):
Full Episodes: https://product-driven.captivate.fm/episodes
Connect with Matt Watson on LinkedIn: https://www.linkedin.com/in/mattwatsonkc/
Subscribe to the Newsletter: https://newsletter.productdriven.com/
Powered by Full Scale: https://fullscale.io/
GET THE PRODUCT DRIVEN BOOK: https://productdriven.com/book
Connect with Brian on LinkedIn :https://www.linkedin.com/in/brianjenney/
Check out Parsity here: https://www.parsity.io/
Key Discussion Points:
“You have to be smarter than the AI.” Why blindly shipping generated code is the fastest way to paint yourself into a technical-debt corner
The hidden risk of non-deterministic models—like failing a simple “greater-than” check in production tests
A training rule of thumb: no AI for your first months of study, then use it only to reinforce fundamentals—not replace them
The “house-of-cards” analogy for code quality and why maintainability still matters when AI writes the first draft
How Parsity’s tight-knit model turns plumbers, teachers, and even doctors into disciplined, product-minded engineers
If you’re running a startup, chances are you’re the bottleneck.
Brittany Rastsmith joins Product Driven to talk through why founders constantly end up in this trap and how to escape it. She works with early-stage companies through her consulting firm, Bloom Remote, and she's seen it all. We get into how to create clarity, visibility, and accountability across your team so you’re not stuck answering every question, solving every problem, or staying up all night wondering if anything is getting done.
If you want your team to take ownership and drive outcomes—not just check boxes—this episode is for you.
[01:00] - Why being the bottleneck it's a stage
[02:30] - Choose your hard: micromanage or build trust
[07:30] - How to measure what matters
[10:30] - Delegating doesn't work if you dump chaos
[14:30] - Explain your thinking if you want your team to carry it out
[16:00] - The power of decision logs and written rationale
[19:45] - Why psychological safety is key to team ownership
[21:30] - Rubber-stamping is the death of progress
[24:00] - Why most managers are untrained (and why that matters)
[28:00] - Productivity vs. busyness: where your team might be stuck
[29:15] - Inputs vs. outcomes: how to tell what's actually broken
[31:05] - Where to find Brittany and learn more about Bloom Remote
Links & Resources:
Brittany Rastsmith on LinkedIn:
Get the Book: https://mybook.to/productdriven
Newsletter: productdriven.com
Connect with Matt: https://linkedin.com/in/mattwatson
Get the Offshore Hiring Guide: https://hirefullscale.com/offshore-hiring-guide
In this revealing conversation, we unpack one of tech's most polarizing concepts while exploring the brutal realities of building technical partnerships in today's startup ecosystem. Host Matt Watson and Noah Lindner (ex-Airbnb engineer turned consultant) deliver unfiltered insights that challenge conventional wisdom about technical hiring and startup team dynamics.
🔗 Essential Links (Start Here!):
Get the Book: https://mybook.to/productdriven
Newsletter: productdriven.com
Connect with Matt: https://linkedin.com/in/mattwatson
Full Scale Ventures: https://fullscaleventures.com
Get the Offshore Hiring Guide: https://hirefullscale.com/offshore-hiring-guide
YC Co-Founder Matching: https://ycombinator.com/cofounder-matching
The conversation opens with a fascinating transformation—how the once-toxic "10X developer" stereotype has evolved into a legitimate business advantage. Noah's perspective shift reveals something profound: the best engineers aren't just writing code faster; they're architecting workflows that eliminate friction entirely.
Real-World 10X Impact:
Matt delivers a game-changing insight: "To really be a true technical co-founder, they've got to have the vision for what's being built... not just the technical vision, but the product vision."
This distinction separates true startup partners from highly-paid order-takers—a critical differentiation in today's competitive landscape.
The conversation reveals how technological democratization is reshaping co-founder dynamics. When any PM can create "lovable prototypes" using no-code tools, the bar for technical co-founders rises significantly. Success now requires scalable prototyping—building MVPs that can evolve rather than require complete rebuilds.
Matt's four-quadrant framework provides clarity:
For early-stage startups, product and technical mastery matter most—operations and strategy complexity come later.
Share Your Story: Tag us with your technical co-founder journey—the wins, failures, and lessons learned. Let's build a knowledge base for the next generation of technical partnerships.
Subscribe for more unfiltered insights on technical leadership, product strategy, and startup team dynamics.
From Coding to Catalyst: The Evolution of Technology Leadership 🚀
Journey through the transformation of modern CTOs with industry veteran Kathy Keating, who shares battle-tested insights from scaling teams of 2 to 450+ engineers. This episode unravels the complex tapestry of technology leadership, exploring how yesterday's code-focused roles have evolved into today's strategic business catalysts.
🔗 Essential Links (Start Here!):
Get the Book: https://mybook.to/productdriven
Newsletter: productdriven.com
Connect with Matt: https://linkedin.com/in/mattwatson
Full Scale Ventures: https://fullscaleventures.com
Get the Offshore Hiring Guide: https://hirefullscale.com/offshore-hiring-guide
The Leadership Evolution Story 📖
The Great Divide: Once upon a time, software engineers were the product owners, customer advocates, and technical architects all rolled into one. They flew across continents to understand telecom fraud patterns, immersed themselves in customer operations for weeks, and returned with deep domain expertise. Today's specialized world has created powerful capabilities—but at what cost?
The Four Pillars of Engineering Leadership: Matt introduces a provocative framework suggesting no one masters all four domains: Strategic visioning, Operational excellence, Technical depth, and Product intuition. The conversation challenges us to identify our strengths while building systems that compensate for our natural limitations.
Behind the Framework: CTO Levels Decoded 🔍
Kathy reveals the methodology behind assessing technology leadership maturity—from solo programmer (Level 0) to industry thought leader (Level 10). Each level demands mastery of previous foundations while introducing new complexities like acquisitions, strategic partnerships, and organizational transformation.
The Assessment Reality: A comprehensive 50-question evaluation generating 60-page strategic roadmaps. Hundreds of leaders have used this framework to identify gaps and accelerate growth—proving that systematic development beats trial-and-error learning.
Chapter Timestamps:
00:00 - Opening: Two Authors, One Mission
02:14 - Defining Modern CTO Reality
04:11 - The Four-Type Leadership Framework
07:21 - CTO Levels: Decoding the Hierarchy
09:25 - Career Path Truth: How Do You Actually Become a CTO?
16:58 - Strategic Advice: The Power of Starting Small
17:52 - Then vs. Now: 20 Years of Engineering Evolution
22:03 - The Product-Engineering Divide Crisis
26:12 - AI Revolution: Promise and Peril
32:44 - Resources: CTO Levels and Liquid Book Overview
33:09 - Final Thoughts and Next Steps
Which of the four engineering leadership types resonates most with your current role—Strategic, Operational, Technical, or Product? Share your experience in the comments and let's discuss how to build complementary teams that cover all bases.
Product Driven: Building Software Teams That Ship Value 🚀
In this special book launch episode, we dive deep into the intersection of engineering leadership, product thinking, and the transformative impact of AI on software development. Join Matt Watson and Craig Ferril as they explore the revolutionary "Product Driven Model" and why traditional development approaches are becoming obsolete.
🔗 Essential Resources:
Get the Book: https://a.co/d/100RmwC
Newsletter: productdriven.com
Connect with Matt: https://linkedin.com/in/mattwatson
Full Scale Ventures: https://fullscaleventures.com
Get the Offshore Hiring Guide: https://hirefullscale.com/offshore-hiring-guide
Key Discussion Highlights:
Chapter Timestamps:
00:00 - Book Launch Introduction & "Find Your Craig"
08:16 - Why AI Makes Product Thinking Critical
15:03 - The Death Spiral of Internal Focus
18:07 - Creating Cultures of Courage vs. Fear
23:14 - The Five Components of Product Driven Model
32:40 - Future of Engineering Leadership
37:22 - Closing the Feedback Loop with Introverted Teams
💡 Key Takeaways:
For Engineering Leaders:
For Product Teams:
For Organizations:
The conversation reveals a fundamental shift happening in software development. As AI democratizes code creation, the competitive advantage moves from "how fast can we build" to "what should we build and why." Teams that master this transition will thrive; those that don't will find themselves building faster in the wrong direction.
💬 Join the Conversation: How is your engineering team adapting to the AI-driven future? Share your experiences with implementing product thinking in technical teams!
🎧 Subscribe to Product Driven for more insights on building software teams that deliver real value.
Special thanks to Craig Ferril for the thoughtful discussion and early feedback on the book. The future of software development isn't just about better tools - it's about better thinking.