Skip to content

Sam Altman Thanked the Coders. The Coders Had Thoughts.

DS
LDS Team
Let's Data Science
8 minAudio · 3 listens
Listen Along
0:00/ 0:00
AI voice
A six-sentence tribute from the OpenAI CEO on March 17 set off a wave of anger among developers who heard it as a eulogy for their profession, not a celebration of it.

Before 9 a.m. on Monday, Sam Altman opened X and typed six sentences. He called out the people who had spent careers writing "extremely complex software character-by-character." He said it was already getting hard to remember how much effort that kind of work actually took. He closed with "Thank you for getting us to this point."

By the time most of the West Coast had made coffee, the replies were on fire.

The post was meant to read as gratitude. Developers read it as a farewell.

The Tweet That Read Like a Eulogy

Altman's full message: "I have so much gratitude to people who wrote extremely complex software character-by-character. It already feels difficult to remember how much effort it really took. Thank you for getting us to this point."

On its face, an acknowledgment. In practice, a trigger.

The phrase "it already feels difficult to remember" did a lot of work. Past tense. As in: that era of craftsmanship is receding in the rearview mirror, and the person driving is Sam Altman.

One user's response landed with particular bluntness: "You're welcome. Nice to know that our reward is our jobs being taken away."

Another wrote: "Nothing says 'you're being replaced' quite like a heartfelt thank you from the guy doing the replacing."

The artist parallel came quickly. Someone wrote: "Also thank the artists who painted complex images stroke by stroke. It already feels difficult to remember how much effort it really took." The parallel was not meant as a compliment.

Digit.in described the energy of the post with precision: "There's a stock villain trope where the antagonist thanks the hero for making everything possible just before the credits roll, and Altman's tweet has that energy — warm, reflective and delivered from a position of total victory."

Futurism called it "a particularly tone-deaf and borderline vindictive missive that suggests Altman has long given up on the idea of fairly compensating content creators and coders for their work."

Why This One Hit Different

Developer frustration with Altman is not new. But this post arrived at a specific moment.

Cursor, the AI coding tool that Anysphere built to sit inside your editor, crossed $2 billion in annualized revenue earlier this month — doubling in three months. Its new Automations feature runs AI agents that write code overnight, while engineers sleep. Cursor's trajectory has become shorthand in developer circles for what the future of software looks like: less typing by humans, more orchestrating by agents.

GitHub Copilot now generates roughly 40% of new code at companies using it. Satya Nadella said AI tools write up to 30% of all new Microsoft code. Altman himself told an audience: "I think in many companies, it's probably past 50% now," referring to how much of the coding work AI handles.

Then, six days before Altman's tweet, Dario Amodei sat at a Council on Foreign Relations event and said AI would write 90% of code within three to six months. He made that prediction a year ago and repeated it in March 2026.

The numbers hit developers where it counts: hiring. Tech layoffs totaled nearly 246,000 in 2025, with the pace accelerating into 2026. Microsoft cited AI as a factor in eliminating roles that junior engineers had traditionally filled. Companies increasingly explain light headcounts by gesturing at their AI toolchain.

Against that backdrop, a tweet from the CEO of the company driving most of this — thanking developers for the work they used to do — landed like a pink slip wrapped in a birthday card.

One technically pointed reply cut through the noise: "The character-by-character discipline produced code humans could audit line by line. AI-generated code at scale removes that. We're trading craftsman-level understanding for velocity, and nobody's accounting for what we lose in security review."

That response captured something the angrier replies did not: the loss isn't just jobs. It is legibility. The ability to understand what your system is actually doing.

The Context Altman Did Not Provide

The tweet arrived about a week after Altman sat for an interview at the BlackRock Infrastructure Summit and admitted the traditional balance between labor and capital was shifting in ways nobody had solved yet. "The next few years are going to be a painful adjustment," he said. He added that the debates ahead would be "very intense and uncomfortable."

He also recently told Fortune that maybe if jobs get wiped out, they were not "real work" to begin with — using a farmer analogy to suggest future generations would look back on today's desk jobs the way we look back at field labor.

The Medium essay "Sam Altman Wants to Sell Intelligence Back to You. Built From Everything You Created" put the critique directly: a company trained its models on code written by developers, art drawn by designers, text written by journalists — without compensation — and now proposes to sell that intelligence back, metered like electricity. The thank-you post, in that reading, is the most honest thing Altman has said: the people who built this are now customers.

That framing got a lot of circulation. One viral response to Altman's thank-you: "Dear devs, You will lose your jobs forever and be forced to work in the coal mines. But you can rest easy knowing Sam Altman is grateful."

The Counterargument

Not everyone in tech greeted the tweet with fury.

Some argued Altman was genuinely reflecting on a transition, not mocking anyone. The charitable read: he was acknowledging that human-written code built the infrastructure AI now builds on top of, and that the labor was immense and real. Gratitude, not gloating.

Altman has also said publicly that developers using AI tools are "hugely more productive" and that the world wants "a hundred times, maybe a thousand times" more software than it currently has. In that framing, AI does not shrink the pie — it demands far more software than humans alone could write, creating roles that did not previously exist.

Some in the AI-optimist camp pointed out that Altman's critics were applying maximum-uncharitable interpretation to a short post. "He said thank you to the people who built the internet," one replied. "The reply guys turned it into a manifesto about genocide against coders."

And Grok, Elon Musk's chatbot, weighed in under the original post: software engineering is "evolving fast" rather than disappearing, with human developers remaining essential for architecture, debugging, integration, and innovation.

Engineers who have ridden AI tools to higher output argue the framing of replacement misses the point. The vibe coding movement — building software by directing AI in natural language rather than writing every line — is producing functional products from non-engineers. But it also demands a different kind of expertise: system design, prompt architecture, debugging AI output. Whether that expertise is "coding" is partly semantic.

What is not semantic is the hiring data. Entry-level software engineering roles are harder to find. Bootcamps report weaker placement rates. The transition Altman called painful is landing unevenly, and the people taking the hardest hit are exactly the kind of developers he thanked.

The Bottom Line

The backlash to six sentences from Sam Altman is not a PR problem he needs to manage. It is a temperature reading.

Developers have spent three years watching the tools they helped build get turned into arguments for hiring fewer of them. They have watched AI leaders predict the end of hand-coded software while selling subscriptions to the companies doing the replacing. They have watched the labor market tighten while productivity benchmarks climb. And they have read, repeatedly, that the solution is to "learn AI" — which is good advice that does not address the structural shift in who gets paid, and how much.

The thank-you post crystallized all of that in a way that policy statements and earnings calls do not. It sounded like an epitaph because, for a lot of developers, the job they trained for is already looking like the past tense.

The most precise response may have come from a developer who wrote simply: "He said 'getting us to this point' not 'getting us here.' To this point — meaning we arrived and he's headed somewhere else. We're not invited."

Altman has not responded further.

Sources

Practice interview problems based on real data

1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.

Try 250 free problems
Free Career Roadmaps8 PATHS

Step-by-step roadmaps from zero to job-ready — curated courses, salary data, and the exact learning order that gets you hired.

Explore all career paths