AI helps developers do new work and learn together
"To Boldly Go Where No One Has Gone Before" What Has AI Let Developers Unlock?
Human-Computer Interaction
Summary
Measuring AI only by how much faster it helps developers misses a bigger question: what new tasks can AI help them achieve? The authors surveyed Microsoft developers who said AI lets them work faster, reach tasks they couldn’t do before, and create new AI-focused work. Developers and AI learn together: AI gets skilled quickly but can’t always judge its work well, so developers need to guide and improve the AI. This cooperation can enrich developers’ skills or make them lose confidence if they rely too much on AI without understanding it.
What this means in practice
- •For software engineering teams: Design development workflows that integrate AI as a learning partner, enhancing skills rather than replacing developer judgment.
- •For ai tool builders: Build tools that support two-way knowledge scaffolding between AI and developers to sustain productive collaboration and prevent skill erosion.
Authors
Rudrajit Choudhuri, Jenna L. Butler, Christian Bird, Carmen Badea, Brian Houck, Anita Sarma
Abstract
Measuring AI by how much faster developers work is like judging electricity by how much faster it spun a steam-era factory. A fuller measure asks what new work becomes possible. We surveyed 331 software developers at Microsoft about what AI lets them do that they could not do before and analyzed their answers using reflexive thematic analysis with a human-in-the-loop, multi-model AI council. Developers described doing familiar work faster (Faster, 45%), undertaking work previously beyond their reach (Further, 36.9%), and taking on new kinds of work centered on building for and directing AI agents (Afresh, 12.4%). Across these accounts, learning and scaffolding ran in both directions: developers learned new skills with AI while externalizing their tacit knowledge as the context and standards that guide AI's work. Drawing on Vygotsky's zone of proximal development, we frame developers and AI as joint learners whose zones meet at the skill-judgment nexus: AI can supply skill faster than it can reliably judge its own work, and developers must continuously bridge that gap. Whether they do sets them on one of two paths. On one, developers' judgment grows alongside AI's skill, and they codify what they learn so the loop keeps turning. On the other, they become hollow orchestrators, approving work they can no longer judge and losing the identity and meaning they once drew from it. Based on our findings, we offer a two-way scaffolding playbook to help developers, teams, and tool builders take the first path.