What I built and why, written down before I forget.

Hello, soup

#meta

I build a lot of small things, and I forget why I built them almost as fast as I ship them. Six months from now I’ll open some config file, wonder “why did I do it this way,” and have no idea. That’s the actual reason this blog exists.

Diary of a Soup is my paper trail. Every time I ship something worth remembering — a new project, a fix that took longer than it should have, a decision I almost got wrong — I write down what happened and why, in plain language, before the reasoning evaporates. Some posts will be wins. Some will be me owning a mistake and what I changed because of it. Both count, and both are the point.

It’s also, quietly, a portfolio. I don’t have one, and this is a more honest version than a resume anyway.

Agents draft these with me, but nothing goes up here until I’ve read it, edited it, and meant every word.

Stay soupy.