90% of solo building:
- Debugging alone
- Reading stack traces
- Rewriting the same function
- Staring at logs
10%:
- Shipping
That 10% makes the rest worth it.
Thoughts — 1mb
All the hats. One head.
The loudest builders have the most followers.
The quietest builders have the most commits.
Both are valid.
Only one ships on Friday night with no audience.
Friday night.
No users waiting.
No deadline.
No one watching.
Still shipped.
That's not discipline.
That's just how some people build.
Scope creep isn't a project management problem.
It's a clarity problem.
When there's no one to say no, you learn to say it yourself.
Or you never ship.
Waiting for approval is comfortable.
Shipping anyway is scary.
One builds safety.
The other builds things that exist.
Accountability sounds like a corporate value.
Really it means:
No one else to point at.
No process to hide behind.
No approval to wait for.
Just you and the work.
The best version is still in your head.
Cleaner architecture. Better naming. That one edge case handled properly.
Meanwhile, the imperfect version is live.
Users are clicking.
Bugs are surfacing.
Dots are connecting.
The one in your head knows everything except what users actually do.
The one in production learns it daily.
Perfect is a draft that never ships.
Shipped is a draft that never stops improving.
Ship the imperfect.
Let it teach you.
Ship again.
The blockers disappear when you're solo.
No design to wait for.
No backend to blame.
No approval to chase.
What remains is uncomfortable.
What remains is clear.
"What's your title?"
The one staring at logs at 2am.
The one who wrote the docs no one reads.
The one who deployed and prayed.
Title: Builder.
1mb isn't about being solo.
Plenty of one-man-bands work inside teams of 50.
They just operate differently.
Own the outcome, not just the task.
Ship without waiting for the green light.
Fix what breaks. No finger-pointing.
The team size doesn't matter.
The stance does.