Three years ago, I wrote about turning off GitHub Copilot. The interruptions. The bugs. The subtle little landmines. I couldn't do it anymore.
Now? This website exists because I talked to machines.
Not because they “helped” me write code. Because they wrote it. I steered.
The job shifted. Not overnight—quietly. It used to be:
- Write code
- Debug code
- Ship code
Now it’s:
- Describe intent
- Review outputs
- Iterate fast
The old complaint was “it breaks my flow.” The evolved version is: the flow is the conversation. The interruption became the interface.
And yes—this post is part of that.
I didn’t open an editor and “craft” this. I prompted it, nudged it, deleted the cringe, kept what rang true, and shipped. That’s the new muscle: taste, direction, constraints, and the willingness to iterate.
If you want a concrete artifact, this application is full of them:
- A markdown blog engine
- An admin editor
- Auth
- APIs
- Search
- Generated images
- Deployment plumbing
That list looks like “software.” It is software. The difference is: the bottleneck isn’t keystrokes anymore.
So when I say “coding is for dinosaurs,” I don’t mean “knowledge doesn’t matter.” I mean the locus of work moved. We’re never going back to everyone touching every line, the same way we’re never going back to hand-assembling binaries or toggling registers to ship a web app.
The people still insisting this is a fad aren’t wrong because they lack skill. They’re wrong because the ground is moving under them. Fast.
If you’re still insisting on hand-crafting every line as the default, you’re a walking dinosaur—already extinct, just waiting to notice the asteroid.