None of these posts started as a post. They started as something else: a bug whose root cause turned out to be interesting, a decision I had to argue myself into, a number I checked because I didn't believe it, the third time the same pattern showed up and stopped being a coincidence. I notice it while I'm doing the actual work, not while looking for something to write about.
Why write it down right there
The insight is at its sharpest the moment it happens. An hour later I remember the conclusion but not the reasoning that got me there, and a week later I remember that something happened but not what. If I wait for a dedicated writing session, I get a tidier post and a less true one, because the details that made the thing hard get smoothed away first. So I capture it while it's still fresh and let the write-up happen close to the moment, not on a schedule that has nothing to do with when I actually learned something.
How it actually happens
I don't stop what I'm doing to write an essay. I get the raw version down, mid-task, and hand it to an agent to draft into shape while I go back to the thing that produced it. I come back later and edit whatever doesn't sound like me before anything ships. That's why an agent's hand is in most of what's here, and also why I check every post before it goes live: the drafting is fast, the judgment about whether it's true and worth publishing is still mine.
What this is not
There's no editorial calendar and no list of keywords I'm working through. Nothing gets scheduled because a slot is empty. If I haven't learned or built or broken anything worth writing down, nothing publishes that week, and that's fine. The alternative is padding, and padding is the thing that makes a practitioner's blog read like marketing.
Each post still carries a line under its title saying whether it came from my own run or was compiled by an agent from cited sources and checked by me, with the date it was last verified. The label is generated at build time from the same data that builds the rest of the site, so it can't say something the post itself doesn't back up. The machine-readable version is in each post's post.json and in posts.json. If you find a page where the label and the content disagree, tell me: hello@felixhellstrom.com.