antirez: "Control the ideas, not the code" - the pivot of the dev profession in the AI era

Ongoing story : La fin de l'ère SaaS ? Agentic + dette technique· Part 4/7

CraftSubscribers only Jul 13, 2026 at 17:277Add to bookmarks

antirez: "Control the ideas, not the code" - the pivot of the dev profession in the AI era — Illustration : Léa Fontaine

Salvatore Sanfilippo (Redis) publishes a short and clear post on what remains for the developer when AI writes the code. His answer: the idea, the architecture, the judgment. The rest is delegable.

In plain terms

antirez, creator of Redis, publishes a short post titled "Control the Ideas, Not the Code". The thesis lies in the title: in an era where AI writes correct code effortlessly, what matters for an engineer is no longer the line but the idea. Control the idea, not the code. Easy to say - much less easy to practice.

The context

For eighteen months, posts about "what remains for devs when AI codes" have multiplied. Most often, they crash against two pitfalls: catastrophism ("we are finished") or naivety ("AI is just a tool"). antirez, with Redis behind him, fits a rare profile: a recognized low-level system engineer who publicly takes a stand on what will remain of a profession. The saas-is-over thread tracks this shift.

Our reading of the thesis

antirez's formulation - "control the ideas, not the code" - points to something we hear whispered in teams over the past 18 months: the value of a senior dev has never been to type the characters. It was: deciding what to build, in what order, with what compromises. The code was just the rendering of these decisions. AI makes the rendering almost free. It does not make the decisions free - it makes them heavier with consequences, because the cost of iteration collapses and the bad choice materializes faster.

The core of the shift

The historical bottleneck of the profession was not the typing; it was the reflection. AI has removed a large part of the typing. It has not removed anything from the reflection - it has made its avoidance more costly.

The analysis

What is at stake - without antirez having to develop it - is a fundamental shift: the profession is sliding from making to directing. The dev who thrives in 2026 is no longer the one who quickly writes a correct dispatcher - the AI does that - but the one who knows why we want a dispatcher, which requests it will serve, what latency, what cost, what degradation plan. The junior who has spent five years typing but never deciding is the most exposed. The senior who has spent five years deciding and never writing is more exposed than he thinks - without the weaving of the code, we lose the sense of the possible.

There is an organizational consequence: flat teams of six seniors led by a tech lead become the winning archetype. Large stratified teams, no.

So what

For a CTO: reconsider the junior/senior ratio on greenfield roles. For a dev: invest in architectural judgment and AI code review - that's where the leverage exists. For a trainer: stop teaching frameworks, teach compromises.