Welcome to DU!
The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards.
Join the community:
Create a free account
Support DU (and get rid of ads!):
Become a Star Member
Latest Breaking News
Editorials & Other Articles
General Discussion
The DU Lounge
All Forums
Issue Forums
Culture Forums
Alliance Forums
Region Forums
Support Forums
Help & Search
General Discussion
Showing Original Post only (View all)The Hidden Costs of Coding With Generative AI (MIT Sloan Management Review, August 18, 2025) [View all]
I missed this when they published it 4 months ago, but they posted about it again on X two days ago:
https://sloanreview.mit.edu/article/the-hidden-costs-of-coding-with-generative-ai/
Generative AI can be a powerful productivity booster in coding but only when deployed thoughtfully. Used carelessly, it can cripple scalability, destabilize systems, and leave companies worse off.
-snip-
When an organization rapidly introduces new software into existing systems, it can inadvertently create a tangle of dependencies that compounds its technical debt that is, the cost of additional technological work that will be needed in the future to address shortcuts taken and quick fixes made during development. Technical debt is the hidden underbelly of digital technology. It is the 60-year-old COBOL code in banking systems that was never properly documented or updated. It is the shortcut of representing the current year with two digits instead of four, leading to the Y2K crisis, which cost hundreds of billions of dollars to fix globally. The buildup of technical debt causes slower development cycles, increased complexity, and security vulnerabilities, potentially leading to system failures.
-snip-
You can think of technical debt as operating much like financial debt. The principal is the work needed to modernize and refactor code; the interest is the ongoing complexity tax that slows maintenance, complicates scaling, and raises the risk of failure. While some debt is unavoidable, implementing AI-generated code is often akin to borrowing at a much higher interest rate. As one of the developers we interviewed said, The problem with AI is that it cant see the big picture. Developers we interviewed also told us about code duplications, integration problems, dependency conflicts, a lack of context awareness, and myriad other problems that come with coding with AI. Indeed, when GitClear analyzed millions of lines of code from 2020 to 2024, it uncovered an eightfold increase in duplicated code blocks and a twofold increase in code churn both measures of declining code quality. The 2024 Accelerate State of DevOps report from Googles DevOps Research and Assessment team found that a 25% increase in AI usage improves code review and documentation but results in a 7.2% decrease in delivery stability. So, what looks like rapid progress today could turn into costly setbacks tomorrow.
-snip-
Letting technical debt compound is dangerous. Southwest Airlines 2022 meltdown which stranded over 16,900 flights and cost the airline over $750 million was rooted in technical debt in its crew-scheduling systems. Technical debt drove the massive 2024 CrowdStrike outage that led to worldwide failures in health care delivery. In May 2025, Newark Liberty International Airport in New Jersey was plagued by massive delays and hundreds of flight cancellations that were caused by a combination of antiquated air traffic control technology and staffing shortages. Failures like these show how invisible risks can suddenly cripple even major organizations. Without deliberate efforts to pay down the principal, organizations risk becoming overwhelmed first slowly, then all at once.
-snip-
-snip-
When an organization rapidly introduces new software into existing systems, it can inadvertently create a tangle of dependencies that compounds its technical debt that is, the cost of additional technological work that will be needed in the future to address shortcuts taken and quick fixes made during development. Technical debt is the hidden underbelly of digital technology. It is the 60-year-old COBOL code in banking systems that was never properly documented or updated. It is the shortcut of representing the current year with two digits instead of four, leading to the Y2K crisis, which cost hundreds of billions of dollars to fix globally. The buildup of technical debt causes slower development cycles, increased complexity, and security vulnerabilities, potentially leading to system failures.
-snip-
You can think of technical debt as operating much like financial debt. The principal is the work needed to modernize and refactor code; the interest is the ongoing complexity tax that slows maintenance, complicates scaling, and raises the risk of failure. While some debt is unavoidable, implementing AI-generated code is often akin to borrowing at a much higher interest rate. As one of the developers we interviewed said, The problem with AI is that it cant see the big picture. Developers we interviewed also told us about code duplications, integration problems, dependency conflicts, a lack of context awareness, and myriad other problems that come with coding with AI. Indeed, when GitClear analyzed millions of lines of code from 2020 to 2024, it uncovered an eightfold increase in duplicated code blocks and a twofold increase in code churn both measures of declining code quality. The 2024 Accelerate State of DevOps report from Googles DevOps Research and Assessment team found that a 25% increase in AI usage improves code review and documentation but results in a 7.2% decrease in delivery stability. So, what looks like rapid progress today could turn into costly setbacks tomorrow.
-snip-
Letting technical debt compound is dangerous. Southwest Airlines 2022 meltdown which stranded over 16,900 flights and cost the airline over $750 million was rooted in technical debt in its crew-scheduling systems. Technical debt drove the massive 2024 CrowdStrike outage that led to worldwide failures in health care delivery. In May 2025, Newark Liberty International Airport in New Jersey was plagued by massive delays and hundreds of flight cancellations that were caused by a combination of antiquated air traffic control technology and staffing shortages. Failures like these show how invisible risks can suddenly cripple even major organizations. Without deliberate efforts to pay down the principal, organizations risk becoming overwhelmed first slowly, then all at once.
-snip-
I remember well-known software engineer Grady Booch posting on X about the technical debt problem with genAI coding over a year ago.
According to this article, the estimated cost of technical debt in the US is already over $2 trillion.
Trillion.
And AI coding is adding to that total cost rapidly.
The article warns that if inexperienced developers are deploying AI-generated code, and if that AI is being deployed in a brownfield (legacy) environment, "it may be best to avoid deploying AI-generated code entirely."
That's a pretty serious warning.
So we have the economy threatened by the AI bubble, and the environment and education threatened by AI as well.
And the coding that underpins much of the economy - and government, for that matter - is threatened by AI coding.
While the surface convenience of AI coding means fewer new developers will be educated, more and more developers will be laid off, and even employed developers will be deskilled by using AI.
But I suppose genAI peddlers and proponents will keep hoping that the hallucinating genAI endangering our coding now will somehow morph into the Magical Non-Hallucinating Coding Chatbot before this digital house of cards comes tumbling down.
10 replies
= new reply since forum marked as read
Highlight:
NoneDon't highlight anything
5 newestHighlight 5 most recent replies
The Hidden Costs of Coding With Generative AI (MIT Sloan Management Review, August 18, 2025) [View all]
highplainsdem
Dec 26
OP
Good for your wife for doing this! I hope her AI-using students learn that they actually need to learn. Wish
highplainsdem
Dec 26
#3
You knew what you were doing. What do you think of the students Diraven described in reply 1?
highplainsdem
Dec 26
#4
??? You mean more nimble competition too smart to use AI coding where it shouldn't be used? This
highplainsdem
Dec 26
#6
