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 Nov 2026
Duration: 00:45:58
Domain expertise amplifies AI's impact on GPU kernel development, while organizations must adapt management practices to attribute costs and distribute individual engineering gains.
This week, Dev Interrupted takes a field trip all the way down to the GPU. Leading the way is Together AI's VP of Kernels Dan Fu, a co-author of Flash...
Dan Fu, VP of Kernels at Together AI and assistant professor at UC San Diego, describes how his team runs the entire inference stack from data center request down to the GPU. He explains that research ideas like "looped models," where a transformer loops back through layers rather than processing them sequentially, now travel from lab curiosity to industry implementation in a far shorter window than during his PhD. A news report that "GPT-6 Astra might be a looped model" illustrated how compressed that gap has become.
The conversation turns to building an AI cloud, drawing an analogy to AWS where infrastructure extends beyond raw compute into databases and logging. Fu emphasizes that "training is a one-time cost in some sense" while value is delivered at inference. He stresses that domain expertise amplifies AI tooling: without deep understanding of the hardware and software stack, AI-generated code "might not be the right code." His team built custom Perfetto and trace viewers to open "windows" into the GPU black box before AI could write kernels at all.
On management, Fu argues that DRI ownership and engineering-manager responsibilities remain largely unchanged, though velocity and AI-spend attribution introduce new failure modes. He frames AI as an accelerant for individual engineers rather than a factory line, warning that concentrating gains in one "1000X" person creates a black hole where visibility is lost.
What if you built a "window" into your system's black box before reaching for AI code generation?
What if you treated your AI tooling spend like a DRI-owned project with a monthly review?
What if you wrote a one-page "agent readme" for your codebase before onboarding any AI agent?
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.
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."
8 Sept 2026 Your agents are starving! Airbytes Michel Tricot on the data ingestion crisis
"Managing SaaS data sprawl requires solving identity reconciliation, standardizing ingestion, balancing agent autonomy with control, and optimizing real-time data for AI reliability, while addressing cultural shifts for AI-driven workflows."