About this site
Because something should explain what the hell is going on here
deadinit.dev is a chaotic-neutral devlog about building startups, breaking builds, and learning things the hard (and hilarious) way.
It’s written by a solo founder / engineer / part-time chaos coordinator who’s juggling product, code, marketing, operations, therapy, and occasionally sleep.
If you’re here, you probably:
- Build weird tools at 1 a.m. because it feels right
- Have more unfinished projects than clean coffee mugs
- Write commits like “ok fr last fix i swear”
- Believe in learning by doing (and redoing... and undoing)
You’re in the right place.
🧠 What deadinit.dev is not:
- A polished playbook on how to “crush your startup goals”
- A fake-it-til-you-raise-it founder diary
- A tutorial site pretending everything works the first time
💀 What it is:
- A living archive of real startup chaos
- A record of wins, fails, pivots, and “huh that actually worked” moments
- A source of insight, humor, and unhinged dev energy
- An open door for other builders who want to learn, relate, or just laugh at our expense
🛠 Built With
This site is likely stitched together with some combo of:
- Markdown, caffeine, and misplaced optimism
- A static site generator that will eventually be replaced
- A CDN that definitely isn’t configured properly
- A backlog of features we’ll “get to someday”
🙋♀️ Who’s Behind It?
Just one very tired dev who keeps rewriting their monorepo and calling it a “pivot.”
Startup experience, terminal trauma, and strong opinions about dark mode.
(👋 You can say hi here or email me if you’re feeling brave.)
If nothing else, deadinit.dev exists as proof that you don’t need to have it all figured out to start building.
Just initialize.
Even if it dies in init().
🧵 Now go read the blog. It’s much better than this page.