Hacker News is arguing that 'coding is solved' by AI agents. Here's what the real adoption, revenue, and benchmark numbers say — and what they don't.

A Hacker News thread this week — amplified into a 178-upvote, 140-comment pile-on over on r/theprimeagen under the title "Hacker News now thinks coding is solved" — has reignited the most tired-but-unavoidable argument in software right now: are AI coding agents actually good enough that writing code, as a discipline, is basically done?

The comment that gets quoted from the original thread cuts both ways: some engineers say AI has meaningfully reduced their maintenance burden and they've stopped caring about the "coding part." Others call the whole discourse "doom scrolling for builders" — noise dressed up as a paradigm shift. Both camps are working from vibes. There's actual data available now, and it tells a much more specific story than either side is arguing.

The Number Everyone's Ignoring: 4% of GitHub

Here's the one stat from this cycle that should matter more than any hot take: analyses cited by SaaStr in February 2026 put Claude Code at roughly 4% of all public GitHub commits, with projections of over 20% by the end of the year. On March 15, 2026, Claude Code hit a single-day peak of 326,000 commits. That's not a curiosity — that's a tool that has gone from a side project inside Anthropic to authoring a meaningful fraction of the world's visible commit history in under a year.

Claude Code launched publicly in May 2025. By February 2026, Anthropic disclosed it had crossed $2.5 billion in annualized run-rate revenue — more than doubling since the start of the year — and that it now accounts for roughly 20% of Anthropic's total revenue. Weekly active users have doubled since January 1, 2026, and business subscriptions have quadrupled over the same window. Enterprise customers now make up more than half of Claude Code's revenue. This isn't a toy adopted by hobbyists tweeting screenshots — it's being paid for, at scale, by companies that presumably measure ROI before renewing.

The Adoption Numbers Are More Interesting Than the Hype

Where it gets nuanced: JetBrains' January 2026 developer survey found Claude Code and Cursor tied at 18% workplace adoption, both trailing GitHub Copilot's 29%. Copilot still wins on raw install base — it's bundled, it's the default, and enterprises don't rip out defaults easily.

But satisfaction tells a different story. The Pragmatic Engineer's February 2026 survey of senior engineers found Claude Code named "most loved" by 46%, versus 19% for Cursor and just 9% for Copilot. JetBrains' own numbers back this up with a 91% CSAT and NPS of 54 for Claude Code — the highest in the category. Translation: Copilot has the seats, but Claude Code has the converts. That gap — install base versus loyalty — is exactly the pattern you'd expect mid-disruption, before the incumbent's distribution advantage gets eroded by word of mouth.

Benchmarks Don't Agree With Each Other, Which Is the Point

If you want a single benchmark to end the argument, you won't get one. Anthropic's Opus 4.6 leads SWE-bench Verified at 80.8%, the highest reported score in the category — a benchmark built around realistic GitHub issue resolution. But on Terminal-Bench 2.0, which weights command-line and DevOps workflows more heavily, GPT-5.5 running in Codex scores 82.7% against Opus 4.7's roughly 69.4% — a 13-point gap in the other direction.

That split matters more than either number in isolation. It means "which AI coding tool is best" is not a solved, single-axis question — it's task-dependent, and anyone citing one benchmark as proof of total dominance is cherry-picking. The tools are diverging by specialty: Claude Code for multi-file architectural reasoning and frontend work with Opus's vision capabilities, Codex for terminal-native DevOps and infrastructure tasks. That's a maturing market with real product differentiation, not a single winner.

So Is Coding "Solved"?

No — and the framing itself is the problem. "Solved" implies the discipline has an endpoint, like a chess engine beating Kasparov. What's actually happening is a redistribution of where developer effort goes. Multi-file refactors, boilerplate, test scaffolding, and a meaningful chunk of DevOps work are increasingly being handled well enough by agents that skilled engineers are choosing to delegate them — hence the "I've stopped caring about the coding part" sentiment in the original thread. That's not the same as "coding is over." It's the same shift that happened when compilers replaced hand-written assembly, or when high-level frameworks replaced boilerplate you used to write by hand. The judgment, architecture decisions, and debugging-when-the-agent-is-confidently-wrong work didn't go anywhere — if anything, it got harder, because you're now reviewing code you didn't write line-by-line.

The Reddit thread's skeptics aren't wrong that there's hype-driven noise in the discourse. But the underlying numbers — 4% of GitHub commits, $2.5B in annualized revenue in nine months, a 46-point satisfaction gap over the previous market leader — aren't hype. They're adoption curves that look a lot like every other infrastructure shift that eventually became invisible because it won.

What This Means If You're Shipping Code This Week

  1. Stop treating "should I use an AI coding agent" as the question. The adoption and revenue data say that ship has sailed for a meaningful chunk of the industry. The live question is which tool for which task — and the benchmark divergence above gives you a real answer, not a vibes-based one.
  2. Weight satisfaction data over install-base data when picking a tool for a new team. Copilot's 29% adoption reflects default bundling and procurement inertia more than it reflects developer preference. The 46% vs 9% "most loved" gap is the more honest signal if you're not locked into an existing enterprise contract.
  3. Budget review time, not just generation time. The bottleneck is shifting from "how fast can code get written" to "how fast can a human verify code they didn't write is architecturally sound." That's a process and tooling problem most teams haven't solved yet, regardless of which agent they've standardized on.

The argument on Hacker News will keep running in circles because it's an identity argument dressed up as a technical one. The commit graphs, revenue disclosures, and benchmark tables aren't arguing about identity. They're just quietly compounding.