#606 AI Can Generate Code. It Still Can’t Replace Engineering Judgment | Jason Li

In this episode of The CTO Show with Mehmet, Mehmet sits down with Jason Li, CTO at Laurel. Jason brings experience from enterprise software, Salesforce, Ironclad, and AI-native product development.The conversation reframes AI adoption away from replacing work and toward understanding work. Faster code generation does not eliminate engineering bottlenecks. Quality, technical debt, review processes, and organizational design are becoming the limiting factors.If you are leading engineering teams, building AI products, or investing in enterprise software, this conversation provides a practical view of how AI is changing software development and technical leadership.About the GuestJason Li is the CTO at Laurel, an AI company focused on time intelligence and productivity. Previously, he worked in enterprise software and held roles at Salesforce and Ironclad.His work spans AI-native products, developer productivity, legal technology, and engineering leadership.His perspective comes from operating AI systems inside production environments while managing the realities of software quality, technical debt, and team structure.LinkedIn: https://www.linkedin.com/in/jasonhli/Laurel website: https://www.laurel.ai/Key TakeawaysAI shifts bottlenecks from code generation to code quality.Visibility into work creates more leverage than blindly automating tasks.Engineering productivity remains difficult to measure despite new AI tools.Agentic coding increases the speed at which technical debt accumulates.Existing code review processes were not designed for AI-generated code.Senior engineering judgment becomes more valuable in an agent-driven world.AI tools expose weaknesses in processes rather than eliminating them.Rewriting software may become cheaper and more common than in previous generations.What You Will LearnThe difference between replacing work and understanding work.How time intelligence creates operational visibility.Why measuring AI ROI remains difficult.How engineering teams are adapting to agentic coding.What skills remain valuable for engineers entering the profession.Why technical debt may increase faster in AI-assisted development.When software rewrites may become preferable to maintaining legacy architectures.Episode Highlights00:00 — Time intelligence extends beyond billing hours03:30 — Visibility matters before automation decisions05:00 — AI should amplify leverage, not replace people08:00 — Trust and reliability determine AI adoption12:00 — AI systems inherit organizational weaknesses15:00 — Measuring AI productivity remains difficult17:30 — Agentic coding changes software engineering20:00 — Engineering leadership becomes more hands-on25:00 — Judgment matters more than coding syntax30:00 — Technical debt grows faster with AI35:00 — Wrappers versus foundation model tools40:30 — Uncertainty creates new opportunitiesListen NowAvailable on all major podcast platforms and YouTube.Connect with the ShowFollow The CTO Show with Mehmet for more conversations at the intersection of technology, startups, AI infrastructure, cybersecurity, and venture capital.