The Structural Shift in Software Engineering: From Writing Code to Orchestrating Systems.

Two months ago, I was living in my IDE. Today, I barely open it.

When Andrej Karpathy writes this week that programming changed specifically this December, not gradually but suddenly, I really felt that too.

Because I’ve lived that shift in real time.

I started as a pure engineer. Heads down. Shipping features. Refactoring. Optimizing.

My leverage was how fast and how well I could write code.

Now? Features are a matter of minutes. Especially since we switched to Codex, I don’t “implement” things the same way anymore.

I spin up agents. I describe what we want in English. I review. I redirect. I decompose problems differently.

The IDE became… the Codex app.

I found myself doing support. Jumping on customers and sales calls. Thinking about positioning. Strategizing on marketing experiments.

Not because I stopped being technical.

But because when product iteration compresses from days to minutes, the bottleneck moves.

The constraint is no longer “can we build this?” It’s: should we build it? Who is it for?

Programming isn’t disappearing.

But “typing code all day” is no longer the core skill.

The real leverage now is 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗻𝗴 agents instead of lines of code. Building the right feedback pipelines.

And if we don’t learn this shift, we won’t just be slightly less productive. We’ll be left behind.