The Repo Is Still Alive
Discipline and depletion produce the same commit log. The tell is not what gets closed — it's whether new work stops getting opened.
#solo
22 posts tagged solo
What You Leave Unlearned
A tool's real cost isn't install and import — it's the weeks to fluency, the upgrade you debug alone. The fastest solo builders learn the fewest.
The green squares tell a story.
Not the one you think.
A commit streak measures showing up. Every day, something. A fix. A README edit. Three hundred days. The graph fills green.
It measures consistency. It does not measure progress.
Two repos. One with three hundred consecutive commits. One with twelve.
The busy one kept the streak alive. Moved buttons. Renamed variables.
The quiet one shipped a migration. A feature still running years later.
The streak is the visible thing. The work is not always.
Proxies work until they become the target. Then you're feeding the proxy.
The streak ends the day you stop committing.
The thing you shipped does not.
No one announced this project.
No launch post. No Show HN. No thread. No landing page beyond the README.
Someone built it. Shipped it. Moved on.
The stars came from people who searched for what it does. Found the repo. Used it. Starred it. Not because someone told them to. Because it solved the problem.
Discovery without a launch.
The building was the launch.
The stars came anyway.
A Lockfile Is a List of People
The unseen maintainers behind transitive dependencies no one chose.
Shipped And Walked Away
Not every project is a garden. Some are monuments — done, shipped, and better off untouched.
The Long Game
A year of solo building is not a milestone — it is what happens when the builder keeps showing up.
The Update
The upkeep no one ships a post about — and most of what keeps a project alive.
The First Bug Report
A failing test is the machine checking its own work. The first bug report is the project meeting someone who never had the context that built it.
The Money Question
Most repos are the gym, not a startup — built to learn, not earn. But some quietly stopped being either.
The Readme
Why the one file written for a human keeps getting skipped — and who pays for it later.
The Graveyard
Every builder's folder of dead projects: not failures, but decisions.
The Oncall
Ship fast, get paged at 3am: the engineer and the ops hat are the same person, six months apart.
Saying No
The rejected list — features declined, integrations passed on — is most of the actual work.
The Design Decision
The gap between "works" and "feels right" — and the designer hat nobody certified you to wear.
The Second Thing
The second project is the first one's rent — proof you can maintain, not just build.
Gist
gist.1mb.devSpec first. Stack later. Describe the idea. Answer the architecture questions. Walk away with a deploy-ready zero-stack spec. $0/month is the architecture, not the budget.
Test Your Own Work
Breaking your own work before anyone else does: the half of shipping nobody teaches.
The Old Project
The quiet project that just runs for a decade — the most underrated kind of shipping.
The Spec
Wearing the PM hat solo: arguing with the only person who can override the spec.
keep building
Not "hustle harder."
Not "scale fast."
Not "10x your output."
keep building
1mb.dev is live.
one-man-band.
All the hats. One head.
Own it end to end.
Ship without waiting.
No newsletter. No product.
Just a quiet corner.
Some build with teams and titles.
Others just build.
This is for the others.