The Installer Is the Manifesto

This tells you everything you need to know about where this is all headed.

If you install Bolt and Bolt installs everything else, you've just been shown the entire argument — compressed into a loading bar, delivered before you've typed a single line of code, over in about thirty seconds.

The installation ceremony used to be where you learned the topology. You'd pull a dependency, it would pull twelve more, you'd google three of them, realize one was deprecated, find a Stack Overflow post from 2019, and thirty minutes later you had a working mental model of the landscape — who owns what, which piece talks to which, where the bodies are buried. It was annoying. It was also, accidentally, an education.

What Bolt is saying — what all of these tools are saying, really — is that the topology is no longer your problem. The map is an implementation detail. You don't need to know what's under it. You just need to tell it what you want and confirm you're not a robot (ironic, given the circumstances).

And look — that's probably fine? Most people never needed the map anyway. They needed a working thing. The map was always a tax on wanting to build something.

But if you do care about the map — if knowing what's under the thing is the actual point for you — then watching Bolt silently configure its own universe is a very efficient way to find out that this particular party has moved on without you.

Not a complaint. Just a diagnosis.

The first sentence of the next era of software development is a progress spinner, and it doesn't need your input.