Eight Myths on Software Engineering and GenAI
- ID: 1a7a5905
- Original URL: https://queue.acm.org/detail.cfm?id=3807963
- Author(s): Jenna Butler, Brian Houck, Margaret-Anne Storey, Travis Lowdermilk, Steven Clarke, Emerson Murphy-Hi...
- Date: 2026-05-26
- Category: coding
- Source type: article
- Tags: software-engineering, genai, developer-productivity, ai-adoption
- Quality score: 4/5
- Fetched at: 2026-08-06T12:26:49+00:00
中文导读
ACM Queue 文章梳理软件工程与 GenAI 的常见误区，指出营销叙事和轶事成功已经领先于证据；文章特别强调开发者并非把大部分时间用于写代码，因此用代码行数衡量 AI 影响会误导工具采纳和组织决策
为什么值得关注
评估 GenAI 编程工具时，组织应避免把代码行数当成生产力本身
This source is useful for AAIF because it turns a current AI adoption/product direction into concrete operational questions: what context the system needs, what evidence should be used to measure value, and which governance boundaries matter when agents move from demos into organizational workflows.
关键信息
- Title: Eight Myths on Software Engineering and GenAI
- URL: https://queue.acm.org/detail.cfm?id=3807963
- Author/source: Jenna Butler, Brian Houck, Margaret-Anne Storey, Travis Lowdermilk, Steven Clarke, Emerson Murphy-Hi...
- Date: 2026-05-26
- Category: coding
- Tags: software-engineering, genai, developer-productivity, ai-adoption
English Summary
ACM Queue examines common myths around GenAI in software engineering, arguing that adoption narratives have outrun evidence, that developers spend only a minority of time writing code, and that lines-of-code metrics can distort how organizations evaluate AI impact.
原文摘要 / Source Excerpt
Eight Myths on Software Engineering and GenAI
原文链接: https://queue.acm.org/detail.cfm?id=3807963
We are redesigning the Queue website. Take a look and let us know what you think.
May 26, 2026 Volume 24, issue 2
Eight Myths on Software Engineering and GenAI
Examining the most common misconceptions
Jenna Butler, Brian Houck, Margaret-Anne Storey, Travis Lowdermilk, Steven Clarke, and Emerson Murphy-Hill
Generative AI is reshaping software engineering—but the narrative has gotten ahead of the evidence. Marketing claims, anecdotal wins, and misread studies have given rise to a set of persistent myths that are quietly driving poor decisions about AI adoption, tooling, and how to measure success.
This article examines eight of the most common misconceptions. We already know developers don’t actually spend most of their time writing code, with studies at Microsoft and elsewhere showing it’s closer to 14 percent. That means AI code generation, even when it works well, touches a surprisingly small slice of the actual job. And yet organizations are doubling down on lines-of-code metrics to track AI’s impact, which is a measure that is neither statistically valid nor meaningfully connected to outcomes such as software quality or delivery speed.
The reality is messier and more interesting than the headlines suggest. AI works better for some tasks, some developers, and some contexts than others. Productivity gains don’t flow automatically from handing engineers a license—they require rethinking workflows at the organizational level. Adoption stalls when developers don’t trust the tools, lack time to learn them, or worry about de-skilling. And the “startups move fast with AI” narrative ignores the compliance, legacy systems, and reliability constraints that define enterprise software.
This article isn’t skeptical, but rather provides practitioners, team leads, and engineering leaders a clearer, research-backed picture so the decisions organizations make about AI are grounded in evidence, not just enthusiasm.
- * *
Generative AI is transforming software engineering at a pace that has outstripped both empirical research and organizational practice. In this rapidly evolving landscape, myths and misconceptions are often amplified by marketing claims, anecdotal success stories, and misinterpreted studies. Drawing on recent large-scale studies, interviews, and field observations, this article highlights eight of the most persistent myths about AI in software engineering, unpacking the evidence behind each one. The goal is to provide a clear, research-backed foundation for understanding AI’s real impact so organizations can make informed decisions about adoption, measurement, and investment.
Myth 1: Developers Spend Most of Their Time Writing Code
Software engineering is a highly demanding job that involves creativity, long periods of focus, much collaboration—and, surprisingly, relatively little time actually writing code. Software isn’t written in a vacuum and, as such, developers need both to spend time independently writing code and in group activities such as meetings, standups, planning, and code reviews. Multiple research projects have looked at how developers spend their days and their time—and the results clearly show that developers don’t spend most of their time coding.
A study of more than 450 engineers at Microsoft in 2025 showed developers spend only 14 percent of their time writing code,11 reflecting what has been found in studies over the years.13,14 One of these studies found that on a “good” workday, engineers spent 18 percent of their time “coding” (not including bug fixing, testing, etc.), while on a “bad” workday, only 11 percent of time was spent coding.13 This highlights how slim the margins can be between a good and a bad day.
A June 2025 study of Microsoft developers looked at their use of AI, and one developer brought up this very point:
“For me, at my level, I do spend a lot of time on design. So like coding is \[one\] aspect, but a lot of time is also spent on design and meetings.”
“I think that and where it’s hard to say, like, I think there’s kind of upper bound on how much of my job I could use it for… And the actual, like, amount of time spent coding… feels relatively small in a week.”
Myth 2: Writing Code Is the Bottleneck
Given the above time distribution, using generative AI solely to assist in writing code addresses only a small fraction of the software engineering workload. If developers spend only about 15 percent of their time typing in the editor, then even an AI assist that makes coding twice as fast would, in theory, improve developers’ overall productivity by less than 15 percent. The other 85 percent of their time remains untouched.
Obsidian Notes
- Content fetched with
opencli web readand written to canonicalcontent/{id}.md. - Chinese guide and relevance note are grounded in the existing AAIF entry plus the fetched source body.
- ACM Queue source page includes article date, authors, eight-myth structure, conclusion, and references.