17 Nov 2026 You cant blame AI for the code you ship | Freshworks Murali Swaminathan
Freshworks uses an AI Product Development Lifecycle to manage code quality and prioritize measurable customer impact over mere tool adoption.
Published 30 Jun 2026
Duration: 00:43:55
Challenges in transitioning AI pilots to production include over-reliance on proof-of-concepts, misalignment with scalable systems, and cultural gaps in engineering practices, requiring disciplined strategies like throwaway code, rigorous testing, early user feedback, and systemic data-driven metrics to align AI with organizational goals through collaboration and infrastructure improvements.
Are you confusing a skyrocketing AI token bill with actual engineering value? This week on Dev Interrupted, Kraken's Engineering Operations Lead, Nik...
The text explores the challenges and strategies involved in transitioning AI pilots to production, emphasizing the risks of over-investing in proof-of-concepts (PoCs) and conflating them with scalable production systems. It highlights the importance of treating PoCs as temporary, experimental tools with a narrow focus on core functionality, rather than as foundations for long-term systems. Key strategies include using "throwaway code" for flexibility, implementing rigorous testing (including agent-based testing), setting high standards for production readiness, and involving real users in validation. Krakens approach underscores that AI accelerates development but does not eliminate the need for structured engineering practices, advocating for a balance between speed and quality, supported by cultural shifts that encourage disciplined AI integration.
Central topics include the integration of AI with testing frameworks to address non-deterministic behavior, isolating PoCs from production environments, and the role of designers in collaborative workflows. The text stresses the need for clear stakeholder communication to manage expectations and prioritize functional prototypes over excessive documentation. Metrics like rework rates, production incidents, and "cost per contribution" are recommended to evaluate AIs effectiveness, avoiding over-reliance on superficial adoption metrics. It also addresses industry trends, such as the shift from AI adoption to validating its value within the software development lifecycle, and the importance of balancing output volume with code quality. Challenges in software pipelines, such as review time bottlenecks, are analyzed through data aggregation and contextual analysis, while tools like Linear B are mentioned as aids for data-driven decision-making.
The discussion emphasizes data as a foundational element for measuring AIs impact, combining quantitative metrics (e.g., cycle time, throughput) with qualitative context (e.g., team dynamics, project goals) to generate actionable insights. It advocates for frameworks that align technical metrics with business outcomes, ensuring stakeholders understand engineering challenges in non-technical terms. Systemic barriers, such as team silos or process inefficiencies, are identified as root causes of delays, requiring data-informed solutions rather than isolated fixes. The text concludes with the importance of intentional AI implementation, leveraging tools and data literacy to drive meaningful, organization-wide improvements while avoiding distractions from misleading aggregated metrics or superficial productivity gains.
What if you use throwaway code for your AI-based PoCs?
What if you automate agent-based testing for your AI systems?
What if you contextualize your engineering metrics for non-technical stakeholders?
17 Nov 2026 You cant blame AI for the code you ship | Freshworks Murali Swaminathan
Freshworks uses an AI Product Development Lifecycle to manage code quality and prioritize measurable customer impact over mere tool adoption.
3 Nov 2026 Bet on research, not on vibes | Together AIs Dan Fu
Domain expertise amplifies AI's impact on GPU kernel development, while organizations must adapt management practices to attribute costs and distribute individual engineering gains.
13 Oct 2026 Building the software factory from the spec up | LinearB's Ariel Illouz & Ofer Affias
"Linear B adopted AI-assisted, spec-driven development, starting small and scaling through structured practices, AI guilds, and iterative refinement, while addressing challenges in code context and engineer role shifts amid rapid industry changes."
29 Sept 2026 Why AI made code review the new bottleneck, and the metric that spotted it | Newsela's Dee Wilcox
"AI's impact on engineering teams is examined, revealing faster development cycles but longer reviews, requiring workflow adjustments, KPI tracking, and iterative testing, while balancing innovation, governance, and quality assurance."
15 Sept 2026 Treat your data pipelines like code, because your agents already do | MotherDuck's Jordan Tigani
"Modern data infrastructure evolves with AI-driven automation, smaller efficient systems, and tools like MotherDuck, balancing innovation, cost, and human collaboration."