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 3 Jul 2026
Duration: 00:36:45
Explores AI and engineering challenges, covering Fables' UX implications, multi-model system complexity, cost-effective model selection, data science hurdles, collaborative work practices, productivity strategies, and trends toward continuous improvements, human oversight, and domain-specific specialization.
This week on the Friday Deploy, Andrew Zigler is joined by Zapiers Kelly Vaughn to dive into the sudden return of Anthropic's Fable model, the realiti...
The podcast discusses the evolving landscape of AI models, emphasizing challenges and considerations in their development and application. Key topics include the unexpected return of Fable, which faced user confusion due to limited access and a benchmarking milestone with its ability to recognize "three R's in strawberry." The discussion highlights the growing complexity of selecting models for specialized tasks, noting the rising costs of highly specific AI tools and the role of internal routing (e.g., directing coding requests to other models) to balance performance and cost. There is also a focus on organizational intelligence, with predictions of increased oversight from institutions due to cybersecurity concerns and the shift toward multi-model systems. The segment explores the transition from large, infrequent model releases to continuous, incremental improvements and the rise of domain-specific models and open-source alternatives that allow customization through fine-tuning.
Data science challenges are highlighted, including difficulties in processing unstructured datasets (e.g., PDFs, logs) and the risks of parameter errors in data transformations. The importance of precise, step-by-step goals for AI agents is stressed, alongside pitfalls in over-engineering solutions, such as assigning unnecessary complexity to identity systems when simpler tools suffice. Collaboration and governance in AI workflows are emphasized, with calls for clear accountability frameworks and the avoidance of "villain bond leadership" in team dynamics. The discussion also addresses workplace disagreements, advocating for collaborative problem-solving over proving correctness. Leadership strategies prioritize empathy, avoiding survivorship bias, and recognizing team contributions, while engineering practices focus on sustainable productivity, backlog management, and structuring workflows to balance major projects with smaller tasks. The role of human oversight in auditing AI outputs and maintaining accountability in automated systems is repeatedly underscored.
What if you decided to re-evaluate your model selection strategy for specific tasks to avoid overspending?
What if you implemented a "human-in-the-loop" process for AI-generated code in your solo workflow?
What if you tackled your data chaos by building a modular, open-source data parser for unstructured data?
Prioritize Model Selection Based on Task Requirements
Evaluate specific use cases before choosing models (e.g., route coding tasks to specialized models like Opus or Sonnet 5 rather than defaulting to Fable for cost and performance balance). Avoid overpaying for general-purpose models when niche tools can deliver better results for specialized workflows.
Implement Minimalist Agent Identity Systems Initially
Start with borrowing user credentials or token-based identities for AI agents instead of building complex, unique ID systems. Use existing tools like API tokens for governance and audit trails, and only scale to advanced systems if specific pain points (e.g., tracking permissions) arise.
Break Down Vague Goals into Verifiable Steps
Define AI agent tasks with precise, step-by-step objectives (e.g., "extract data from PDFs in this format") rather than using vague directives. This ensures agents can process data accurately and aligns with engineering practices that prioritize measurable outcomes.
Automate Code Quality and Backlog Prioritization
Use linting tools and automation to fix code issues and ensure tests pass. Regularly clean engineering backlogs by segmenting tasks into "big rocks" (critical projects) and smaller throughput tasks (e.g., code reviews), avoiding overloading critical workflows with low-priority items.
Integrate Human Oversight in AI Workflows
Audit AI-generated code and legacy systems regularly to catch errors and maintain context. Avoid over-reliance on untested models by involving humans in decision-making, especially for high-stakes tasks like data joins or complex transformations.
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."