Build the thing.
Don't build the system
that builds the thing.

I spent months perfecting a Notion workspace. Color-coded databases, linked views, automation triggers. It was genuinely impressive. Nothing got built.

The system had become the work. I was optimizing the container instead of filling it. The fix wasn't a better system — it was subtraction. Journal. Execute. Repeat.

The tool that disappears tomorrow should leave you inconvenienced, not paralyzed.

That's my honest test for any tool, any stack, any AI integration. If removing it exposes you — if the work stops without it — then somewhere along the way the tool stopped serving you and started owning you.

AI is different in kind, not just degree. It's a substrate shift — the way electricity was a substrate shift. But the same rule applies: adopt in a way that you can still set it down. Use it to extend what you can do, not to replace what you should know how to do. A scientist with a microscope sees further. A scientist who forgets how to observe without one is a different problem.

The best tools are portable dependencies. Easy to pick up. Easy to set down. Replaceable without identity crisis. That's what I try to build here, and it's how I think about everything I build for other people.