Skip to main content

Command Palette

Search for a command to run...

Understanding Collapse: A Comprehensive Guide

Discovering the Reality of Creating from Survival and How It Can Help Others

Updated
3 min read
Understanding Collapse: A Comprehensive Guide

After Collapse Compiles

The first post sounded clean. Cleaner than real life ever is.

Real life looked more like this:

Half-charged phone. Nowhere quiet. Body hurting in ways that don't show on the outside. Trying to remember dates and symptoms and conversations while your brain is busy just keeping you upright.

That's where this thing actually came from.

Not vision. Not ambition. Just the slow realization that if I didn't start writing things down, nobody would ever believe what was happening — and eventually I might not believe it either.

So I built something to remember for me.

Not in some company's cloud. Not behind a login I could lose. Just… here. On the device in my hand. Where nobody else gets to touch it unless I say so.

That decision wasn't technical. It was emotional. And honestly, a little paranoid. But the kind of paranoid you earn.


The part nobody puts in tech stories

Some of this code was written on days that had nothing to do with coding.

Days about court dates. Money stress. Places to sleep. Trying to stay steady enough to show up for my kid and not let him feel how close everything was to falling apart.

You don't think about architecture patterns in moments like that. You think about survival.

And weirdly… writing code helped. Because code is predictable. It either works or it doesn't. It doesn't gaslight you. It doesn't forget what you told it yesterday. It doesn't change the story halfway through.

Real life does.

So I kept coming back to the one place where cause and effect still made sense.


Why the privacy thing is so intense

People read "local-first" and think it's a design trend. It's not.

It's what happens when you've seen information move in directions you didn't choose and suddenly your own story isn't yours anymore.

Health data is the worst version of that. Because you can't change it. You can't rotate it like a password. Once it's out, it's out forever.

So yeah — I'm stubborn about it staying on the device.

Not because it's elegant. Because it feels safe. And safe is rare enough that you protect it hard.


The weird shift happening now

Something changed recently, and I don't totally know how to talk about it.

At first this was just… mine. A survival tool. Private. Small.

Now there's this quiet question sitting in the background:

What if other people actually need this?

That's heavier than building for yourself. Because if you screw up alone, it's just your problem. If someone else relies on it… different story.

So everything slows down. Decisions matter more. Shortcuts feel dangerous.

It stops being therapy through code and starts being responsibility.

I'm still getting used to that.


The one thing underneath all of it

There's a lot of complicated context around this project. Legal stuff. Housing stuff. Health stuff. History that doesn't fit nicely into a blog post.

But if I strip it down to the real core, it's simpler:

I have a son. He still looks at me like I'm supposed to be okay. Like I'm someone solid.

And when everything else felt unstable, building something real — something that worked — was one of the only ways to stay that person.

Not perfect. Just… still here.


So what does "after collapse" mean?

Not victory. Not some clean redemption arc. Life isn't a movie.

It just means this:

Things didn't end where they could have. Something useful came out of a period that mostly hurt. And the story kept moving instead of stopping.

That's it.

Nothing inspirational. Just true.


Pain Tracker — Private pain tracking that stays on your device. No cloud. No company. Just yours.