People ask me how I manage to keep shipping while working alone. The honest answer is that I stopped trying to build perfect things and started building complete things instead.
That mindset shift changed everything.
The Trap of the Unfinished Project
Most solo developers I know have a graveyard. A folder somewhere full of half-built apps that were exciting for two weeks and then stalled. The UI is half-done. The auth works but nothing else does.
I lived in that graveyard for years. The moment I started shipping on a weekly cadence, the graveyard stopped growing.
What "Shipping" Actually Means
Shipping does not mean launching a polished product. It means putting something real in front of real users. A landing page with a waitlist is a ship. A functional MVP with three core features is a ship.
The bar for "shipped" is: can a stranger use it? If yes, you shipped. Everything after that is iteration.
My Weekly Rhythm
Monday and Tuesday are for scoping. I pick one thing to build — usually from a list of annoying problems I have personally experienced. I write out the simplest possible version that would be genuinely useful.
Wednesday through Friday are for building. Three days of focused work. No feature creep allowed.
Saturday is for shipping and writing. I deploy, write about what I built and why, and share it.
Sunday is off. Completely.
The Tools That Make It Possible
My stack stays consistent across projects so I am never learning infrastructure while also building a product. TypeScript, a framework I know deeply, a deployment target I can push to in under a minute. Familiarity is a velocity multiplier.
I also keep a running doc of reusable patterns — auth flows, payment integrations, API scaffolding — that I can drop into a new project without rebuilding from scratch.
What I Have Learned From Shipping
Most ideas that feel big are actually small. The feature you think will take a week takes a day. The part you thought was easy takes three days. Shipping quickly surfaces these realities before you have sunk months into wrong assumptions.
Users tell you things you could never have predicted. The feature you thought was core, nobody uses. The thing you built as an afterthought becomes the reason people come back.
And momentum is real. Shipping something creates the energy to ship the next thing.
Where I Write About This
I document the whole process — what I built, what broke, what users said — over at The Dolce Way. It is part build log, part reflection on the indie developer life. If you are trying to ship more and finish more, there is a lot there that might help.
The short version: scope small, ship early, write about it. Repeat.
Read more at thedolceway.com.
Top comments (0)