
Show Notes
Developer productivity is often framed as a tooling initiative or a morale issue. At scale, it’s a more complex socio-technical systems challenge that spans engineering foundations, leadership alignment, organizational structure, and culture.
In this episode, Laura Tacho sits down with Uma Namasivayam, Senior Director, Engineering Productivity at Dropbox, to discuss how the company approaches developer experience across an organization of nearly 1,000 engineers. Uma explains why productivity must be treated as a business problem, how executive alignment enables sustained progress, and what it means to run developer experience like a product. The conversation also explores the intersection of AI and developer experience. Uma shares how Dropbox prepared its engineering systems to support AI adoption, why daily AI use depends more on habits than access, and how the company evaluates build-versus-buy decisions as AI tools struggle to scale in large environments.
The episode concludes with a candid discussion of the open questions facing engineering leaders today: how to understand where AI-driven capacity actually goes, and how to connect improvements in developer experience to meaningful business outcomes in 2026.
Where to find Uma Namasivayam: • LinkedIn: https://www.linkedin.com/in/unamasivayam
Where to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/ • X: https://x.com/rhein_wein • Website: https://lauratacho.com/ • Laura’s course (Measuring Engineering Performance and AI Impact) https://lauratacho.com/developer-productivity-metrics-course
In this episode, we cover: (00:00) Intro (00:45) Dropbox’s engineering org (01:59) Why developer productivity is a business problem (04:08) The role of executive sponsorship in developer productivity (06:02) How DX’s Core Four framework created a shared language (08:13) Treating developer experience as a product (11:30) How Dropbox prioritizes developer experience work (14:20) The challenge of tying developer experience to business outcomes (16:38) How AI and developer experience intersect at Dropbox (18:35) The prerequisites for AI adoption to accelerate work (20:26) How Dropbox encourages daily AI use (23:12) AI use beyond code completion (25:00) Managing AI tool demand at scale (27:56) Early results from Dropbox’s AI efforts (30:05) Progress on developer experience at Dropbox (32:55) Advice for organizations investing in developer experience (34:25) Capacity tradeoffs for developer experience (35:59) The unanswered questions around AI and capacity in 2026
Referenced: • DX Core 4 Productivity Framework • Dropbox.com
More from Engineering Enablement by DX
As AI agents become more capable, context quality is increasingly the limiting factor in their performance. In this episode of Engineering Enablement, DX researcher Brian Houck by his CAFE(S) is joined by co-authors Max Kanat-Alexander (Capital One), Eirini Kalliamvakou (DX), and Margaret-Anne Storey (University of Victoria) to discuss CAFE(S), a new framework for improving context quality. The panelists introduce the five dimensions of CAFE(S): Clarity, Actionability, Fidelity, Efficiency, and Security. They walk through common context failures, how poor context accrues technical and cognitive debt, what it costs in developer productivity and operating spend, how AI is changing the skills engineers need, and why context review could become as important as code review.
Meta researcher Moritz Beller joins Brian Houck to discuss how Meta measures developer productivity. Moritz explains diff authoring time and how Meta uses it to evaluate tools and guide engineering decisions. They explore how AI is changing engineers’ work and revealing gaps in traditional metrics. They also revisit Moritz’s “Mind the Gap” study and discuss the promise and risks of AI agents for testing.
In this episode of Engineering Enablement, Robert Lucero, Chief Architect at Okta, joins host Brian Houck to discuss how agentic AI is changing identity and access management. They explore how organizations should define agent identities, why authentication and authorization remain foundational, and how sandboxing, fine-grained permissions, and just-in-time access can enable agents to operate autonomously without creating unacceptable risk. Robert shares what Okta has learned from driving AI adoption among security-minded engineers, what makes a repository ready for AI agents, and why strong testing, CI, and review processes matter even more as AI generates more code. They also discuss AI’s role in software validation, the need for human judgment, and whether AI will ultimately give the advantage to security teams or attackers.
Max Kanat-Alexander is an Executive Distinguished Engineer at Capital One, where he helps lead developer experience and AI-assisted software development. In this episode of Engineering Enablement, Max joins Brian Houck to discuss how AI is changing software development and why strong engineering fundamentals matter more than ever. They explore how engineering skills are evolving, why AI can amplify weaknesses in the development lifecycle, and how teams should rethink code review, quality, and testing. Max also shares how leaders can assess whether their organizations are ready for more advanced AI workflows and why developing the next generation of senior engineers remains one of the biggest open questions in software engineering.
AI adoption among software developers is approaching 100%, AI-authored code now makes up more than half of merged code, and developers report saving more time with AI every quarter. But those gains aren’t translating evenly into better outcomes. In this episode of Engineering Enablement, host Brian Houck, Distinguished Scientist at DX, sits down with Justin Reock, Deputy CTO at DX, to unpack findings from DX’s latest AI Impact Report. They explore where AI is improving engineering velocity and developer experience, where concerns are emerging around PR size, change confidence, and failure rates, and why rising AI spend has yet to produce a comparable increase in innovation. They also discuss how AI is changing the meaning of code maintainability and where developers’ AI-driven time savings may actually be going.