Netlify CTO says coding is dead — HN asks if she ever coded

“Writing Code Is No Longer the Job” — and the Thread Begs to Differ

At some point in 2026, most major cloud platform CTOs are required by law to explain why AI means that developers are now something else. Netlify's Dana Lawson delivered her version to The New Stack on June 6, and the article produced one of the tighter ratio numbers on HN that week: 49 comments on 41 points, meaning almost every voter had something to say.

What Lawson Actually Claimed

The article — which sits behind a soft paywall — lays out Lawson's argument that the engineering role is shifting from writing code to orchestrating AI agents. She introduced the frame "UX + DX = AX" (agent experience), positioning Netlify as a platform for this new discipline. She predicted a billion new applications by 2029, driven by the reduction in the friction of software creation. The implication for engineering teams is that "writing code" is the means, not the end, and that AI has made the means largely automated. Engineers, in her telling, now design the systems that write the code rather than writing it themselves.

The Thread Reads the Résumé

In the thread, the first reversal was biographical:

"Looking at Dana Lawson's career on LinkedIn, it looks like they never spent time being an actual developer. Seems fitting that a completely out of touch elite in the US would make such statements." — an HN commenter

This is a pointed but not entirely fair critique — CTOs at platform companies often come from product and operations backgrounds. But it crystallized a second, more substantive objection that multiple commenters circled independently:

"It was never the job as long as the profession was called 'software engineer' and not 'coder'." — a Zurich-based engineer

"Writing code was never the job. Writing code was always a means to the job. This is why people hire 'software engineers', not merely 'programmers'." — a startup founder on HN

The sharpest structural critique came from a commenter who named the actual problem Lawson's framing obscures:

"I think a lot of developers aren't aware that pretty much all non-IT businesses people, from receptionists to the C-suite, really do think that what IT people do is take their brilliant, fully formed ideas, and just convert them into 'computer language' so the computer does them by magic. There's no understanding that almost the whole job is trying to figure out all the assumptions, corner cases, logic conflicts, etc. embedded in their 'requirements'. This is why IT is always seen as just an overhead cost to cut as much as possible." — a veteran developer on HN

That reading suggests Lawson's claim isn't new insight — it's the oldest executive misunderstanding of engineering, now dressed in agent-experience language.

A historically-minded commenter added the context that makes the prediction look less bold:

"A lot of the AI hyping sounds like the cloud and serverless hyping… I remember I had a VP of engineering at a company a while ago I got into a fight with about cloud. Their argument was that cloud economics were such that on-premise was dead dead. My argument was that it could still be considered an engineering question. And while I'm not saying on-prem is winning; it's not a foregone conclusion as 37signals has discovered." — a platform engineering manager

One commenter offered the cleanest satirical reductio:

"Being a Chief Technology Officer is no longer the job. We now need an end-to-end AI orchestrator for the corporation in the Chief Agentic Officer role." — an HN commenter

The Billion-App Number and the Netlify Context

Lawson's "billion apps by 2029" figure deserves scrutiny. The Apple App Store currently holds roughly 2.36 million apps. Reaching a billion would require a 400x expansion — not in downloads, but in distinct applications. One HN commenter did the arithmetic and noted that even if every person on Earth wrote ten apps for personal use with AI assistance, you'd approach the number only if you count throwaway tools. The more interesting counter-prediction appeared in the thread's most sardonic comment:

"Netlify CTO in 6-18 months: that vibe project that caused me to say writing code is no longer the job got so unmaintainable that I hired a team of 3 to take it over. They're rewriting it by hand because tokens are too expensive now. Nobody could have seen this coming." — an HN commenter

Meanwhile, at least one commenter reported leaving Netlify entirely: "just last week we moved away from netlify to our own solution on AWS. Services like netlify who are a layer on top of AWS are no longer needed." The CTO of a platform losing customers to raw cloud infrastructure has every incentive to declare that the platform era is over and a new, higher-value era is beginning — one where Netlify is positioned for the new paradigm rather than obsoleted by the old one.