The Return of the Deferred Builder
For experienced technologists with ideas, taste, judgement, and half-finished projects...
I’ve started thinking about a certain kind of experienced technologist as a deferred builder.
They are not beginners. They are not short of ideas. In many cases, they have better taste, broader context, and sharper instincts than they had twenty years ago.
But somewhere along the way, they stopped shipping small things.
Not because they stopped caring about technology. More often, their work became operational: meetings, architecture, reviews, risk, strategy, management, incident response, governance, delivery pressure, and the slow accumulation of unfinished admin.
The ideas didn’t disappear. They just stopped having somewhere to go.
That is the motivation behind Shipping Again.
The site is for people who still have ideas, judgment, and technical instincts, but no longer have the old rhythm of building every evening or burning a weekend to push something over the line.
Over time, many of those people quietly accumulate abandoned side projects, half-finished repositories, domains bought years earlier, notebooks full of ideas, and internal “one day” lists.
Then coding agents arrived
Not in the dramatic “AI replaces engineers” sense, but in a much more practical one.
Coding agents did not make me want to build again. They made building feel reachable again.
That distinction matters.
Coding agents are already good at producing a first pass. Sometimes surprisingly good.
But moving beyond the first pass still takes judgement. You need to know what to ask for, what to test, what to distrust, and how to steer the agent from plausible answers toward ground truth.
That is where experienced technologists have an advantage.
The useful shift is not that quality software suddenly became effortless. It is that many of the friction points around small projects became smaller: setup, boilerplate, glue code, framework archaeology, wiring things together, and getting from idea to first working prototype.
That disproportionately benefits people with broad context, decent taste, and limited uninterrupted time.
Shipping Again is built around that idea.
Not hustle culture.
Not “build a startup in 30 days.”
Not productivity theatre.
Not becoming an “AI influencer.”
I’m much more interested in second-act building: experienced people using better tools to revisit deferred ideas at a sustainable pace.
In conversations about this topic, I kept coming back to the same rhythm:
experiment → decide → ship → release
Not grindset culture. Not performative busyness. Just a practical way to move ideas out of notes, bookmarks, domains, and abandoned repos — and into small useful things that compound over time.
That might be:
- a weekend project,
- a small internal tool,
- a niche website,
- a weird automation,
- a research notebook,
- a polished explanation of something you’ve spent years understanding.
The project itself matters less than rediscovering the habit of making things.
I suspect there are far more deferred builders out there than we realise.
People who never stopped being technical.
They just stopped shipping.
That’s what Shipping Again is for.
Small projects. Sustainable pace. Second-act building.