enricosf ~/writing/the-orchestra-doesnt-play-itself %
Pick brand, product or code to check out that branch. Pick main to see everything.

d7e2a90 · docs(writing) · HEAD → writing

The orchestra doesn't play itself

There's a narrative going around that AI is proof developers and designers are no longer needed. That take gets it completely backwards.

AI doesn't replace the people who build systems. It eliminates the work that was always in the way of building them well.

Those problems are solved

Think about how any experienced engineer actually works. They don't write auth from scratch. They don't rebuild a messaging system from zero. They pull battle-tested libraries, established frameworks, proven components. Because those problems are solved. Their value was never in the repetitive execution. It was always in the architecture, the judgment, the decisions that actually determine whether a product succeeds or fails.

AI is just the next layer of that same logic.

Not in the boilerplate

What it actually does is return your focus to the 10-20% of work that genuinely matters. The problem you're solving. The flow a user moves through. The architecture decisions that will either hold or collapse at scale. The experience that makes someone come back.

That's where products are won or lost. Not in the boilerplate.

The knowledge moved upstream

The people who will struggle with AI aren't the developers or designers. They're the ones who expected a one-click solution to what teams and months used to produce. They never understood that the knowledge requirement didn't disappear. It just moved upstream.

AI is an orchestration tool. And orchestration still requires someone who understands the system.

Like an experienced conductor. The orchestra doesn't play itself.

drag the mark to turn it