Skip to content

// essays · 10 November 2026 · 2 min read

We didn’t mind abstraction until it started writing itself

Every layer of software history is an abstraction we agreed to stop seeing.

Photo by Joshua Hoehne on Unsplash

Every layer of software history is an abstraction we agreed to stop seeing. Machine code gave way to assembly. Assembly gave way to C. C gave way to the higher-level languages most of us write in today, JavaScript included, itself sitting on an interpreter, a runtime, a compiler chain, none of which we think about while writing a for-loop. We didn’t just tolerate each of those trades. We adopted them the moment they made us faster, and stopped looking back down the stack almost immediately.

We’ve made this exact trade before.

Nobody today writes assembly to build a web app, and nobody mourns that. The abstraction didn’t threaten the craft, it just moved where the craft lived. Compilers took over register allocation, and we were fine with it. Garbage collectors took over memory management, and we were fine with that too. Every one of these was, at the time it shipped, a program writing more of the program than a human did directly.

The only thing different now is who’s holding the pen.

Andrej Karpathy said it plainly back in January 2023: the hottest new programming language is English. What’s actually new with a coding agent isn’t abstraction, it’s that the interface moved from a formal language to English, exactly as he called it two months after ChatGPT shipped. That’s a real distinction, not a fake one. C compiles to the same binary every time. A prompt doesn’t reliably produce the same code twice, and that unpredictability is a legitimate, specific complaint, not nostalgia dressed up as rigor. But notice what that complaint is actually about: determinism, not abstraction. We’ve had non-deterministic systems before too, any distributed system, any ML pipeline, and we didn’t declare computing over. We built verification around them instead.

So the panic isn’t really about the abstraction. It’s about who’s still allowed to call themselves the author.

Assembly programmers didn’t lose status when compilers got good, they just stopped being the only people who could ship software. The same thing is happening again, one layer up, and the discomfort reads less like a technical objection and more like the first time the abstraction climbed high enough to reach the identity, not just the syntax.

We didn’t ask every previous layer to prove itself deterministic before we used it. We asked if it made us faster, and then we used it. Pick the standard you’re actually applying, and apply it going backward too.

Muhammad Mairaj is a Senior Backend Engineer with 8 years building payment and data systems. He writes about data engineering, measured. More about him.