"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.
All the hats. One head.
"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.
"End-to-end ownership" sounds corporate.
Really it means:
You designed it. You defend it.
You broke it. You fix it.
You shipped it. You support it.
No handoffs.
No blame.
Just outcomes.
PM wrote the spec.
Designer questioned it.
Engineer built it.
QA tested it.
User broke it.
Support answered the ticket.
Same person.
All the hats. One head.
No membership.
No Slack.
No newsletter.
Just a question:
Do you own it end to end?
Do you ship without asking permission?
If yes, you already know what 1mb means.
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.