Introducing the ZeNorm blog
A place for the long-form writing that does not fit in a changelog entry, plus product updates that explain the why behind a release.
We now have three places where we write things down, and they do different jobs.
The changelog stays what it was: the line-by-line list of what shipped. Added, fixed, changed. If you want to know whether a bug you reported is out, that is the page.
Product updates — this page — is for releases that need a paragraph rather than a bullet. Why we built a thing, what it changes about how you work, and what we deliberately left out.
The blog is for writing that has nothing to do with our release cycle: what breaks when you hand implementation to a coding agent, and what to do about it. It launches with ten articles on context loss, review, scoping, and specification drift. Most of them do not mention ZeNorm at all.
Why bother
Every team we talk to is running into the same wall from a different direction. The agent gets a feature most of the way there and then stalls. The spec says one thing and the code does another. The tests are green and prove nothing. None of that is a ZeNorm problem — it is what building software with agents currently feels like, and there is not much written about it that goes past the surface.
So we are writing it down. If a post is useful and never mentions us, that is a good post.
Subscribing
Everything is in the RSS feed. No email capture, no newsletter modal.