AI and the Midas problem

AI and the Midas problem

BackerLeader ●19 ●157 ●266
calendar_today ago • schedule4 min read
— Originally published at thenewstack.io

When feature factories use AI, everything they build turns to ash.

Every team that adopted Claude Code, Cursor, or Copilot to produce more code has the same problem. When output is free, volume stops being a viable strategy. In fact, teams accelerating their software development with AI may be giving up the very thing that makes their software valuable.

It’s time to remind ourselves of the things that make software valuable and why racing to produce a mountain of code and features is the path to failure.

The Midas touch

In Ovid’s tale, Midas, king of Phrygia, found the missing satyr Silenus, granted him ten days of hospitality, and then returned him to Dionysus. In return, he was offered the reward of his choice; he could have whatever he could wish for. Famously, he wished that everything he touched would turn to gold.

Testing his new ability on an oak twig and then a stone, Midas was delighted. He returned home and turned his rose bushes to gold, still delighted though the bees were alarmed. Celebrating his superpower with a feast, he discovered food and drink turned to gold in his hands. That’s when Midas realized his reward was a bane, not a blessing, and asked to be rid of it.

Though the process is gradual, many organizations and leaders who force-fed AI to developers are now coming to a similar realization. There are reports of organizations squashing budgets, limiting tool use, and regretting the fallout from AI-related incidents. With Microsoft, McKinsey, Meta, Palantir, and Nvidia all found within the list of organizations rapidly backpedalling on AI, it’s time to acknowledge that the return on investment might not be there, and it’s easy to understand why.

The economics of plenty

If Midas had depended on the value of gold, perhaps hoping to trade the gold he created to fund his lavish lifestyle of hosting ten-day-long parties, he would have quickly learned that his gold was no longer valuable. His touch would cause hyperinflation and the price of gold would plummet. His skill would be as useful as being able to turn everything you touch to ash.

In the modern and non-mythical world, everything you touch with AI turns into a commodity. If you can get Claude or ChatGPT to create something for you, so can everyone else. They have access to the same tools. Whether you’re building software or writing a book, when you use AI its perceived value is little more than the cost of the tokens you used.

When coding looked like magic to most people, basic coding competence used to be sufficient value. You could build a career in translating human language requirements into code. This value rolled up to the team, department, and organization level, with code magicians performing their arcane translations in return for money, whether the software was internal, built for a customer, or sold as a product.

If your software is an expression of user requirements translated into code, it’s now worthless. We know that a page that adds nothing beyond the AI summary is worthless, and software built through the translation of a user’s wants into code is just the same.

How to avoid incinerating your software’s value

There is hope for us, though. When Midas asked to be rid of his power, he had to wash in the Pactolus river. Our touch isn’t directly connected to the generation machine, which means it’s not inevitable that our touch will turn our work to ash.

The answer is actually quite simple conceptually, though it takes high effort in practice, which seems to be the very thing people wish to avoid. Nevertheless, for your work to be immune to the mortally ruinous touch of AI, you need to provide something over and above what someone could achieve with their own Claude subscription.

That means moving away from the feature-factory model of software development, where the value is primarily in the translation of “human wants: into code. Instead, teams building software must build a deeper understanding of the jobs users are doing and their challenges, so they can come up with novel ideas and commercial insights that the user wouldn’t reach alone.

This second mode of building means you may deliver something completely different from what users ask for, but which gracefully solves many of the challenges they face in their work. The combination of deep knowledge of the business domain and an understanding of abstract re-usable solutions means you can deliver something exceptional.

DORA’s State of DevOps research has highlighted this need for user-centricity. That doesn’t mean doing whatever users ask, it means understanding their work and challenges so you can provide software they value. This approach results in higher product performance, irrespective of delivery speed.

We are living through a time of excess in terms of code, sentences, and images. The path forward isn’t more; it’s better.

Cover photo by Agustín Ljósmyndun on Unsplash.

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

Local-First: The Browser as the Vault

Pocket Portfolio - Apr 20

The Esoteric Realms of Code

nevmenandr - Nov 14

The Languages of Machines and Humans: A Developer's Perspective

nevmenandr - Nov 4

The Sovereign Vault — A Comprehensive Guide to Protocol-Driven AI

Ken W. Algerverified - Jun 4

A Textile Mill's Dyehouse Ramp Curve: Get One Step Wrong and the Sheet Belongs to the Master

aiomniu - Oct 18
chevron_left
17.2k Points • 442 Badges
113Posts
179Comments
132Connections
Steve Fenton is an Octonaut at Octopus Deploy. He’s a Software Punk, author, programming-architect, ... Show more

Related Jobs

View all jobs →

Commenters (This Week)

6 comments
2 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!