It has never been about code

The claim

In a recent long-form essay, it has been reported that software veteran Uwe Friedrichsen argues the story of computing has always been about more than syntax and compilers — it’s been about practices, processes and people. The piece traces a familiar origin myth — Lovelace, Babbage, Turing, von Neumann — then pivots: the struggle was never only to build a universal machine but to make human intentions legible to it. Frustration, patience and layers of abstraction followed. Who hasn’t felt that pain? It’s the emotional core of the essay: the dream of automation and the grind of getting a machine to understand what you mean.

Historical grounding

Friedrichsen walks readers through the arc: machine code, assembler, third‑generation languages, and repeated attempts at higher‑level escapes — 4GLs, model‑driven approaches, low‑ and no‑code. It has been reported that his point is straightforward: none of those promised revolutions really displaced the day‑to‑day reality of writing in 3GLs. That’s not nostalgia; it’s a lesson about what actually scales in organizations, where habits, tooling and institutions shape outcomes more than language design or flashy abstractions.

AI asking fundamental questions

Now throw AI into the mix. The essay — and the conversation around it on community sites — alleges that generative systems are forcing us to revisit the real bottlenecks: specification, review, collaboration, and accountability. Code generation is seductive, but does it solve the messy human problems that have always lurked behind the keyboard? Not yet. The implication is stark: improving software means improving practices, not just producing better parsers. Sound familiar? It echoes recent debates about governance and the limits of tool‑first thinking.

Bottom line

The takeaway is both simple and uncomfortable: write less about lines of code and more about how people work together to translate intention into action. It has been reported that Friedrichsen’s essay landed on Lobsters and sparked a lively thread because it reframes a technical debate as a human one — and that’s where the next big leaps will likely come from. Want a revolution? Fix the practices. The code will follow.

Sources: ufried.com, Lobsters