Making the case in public

The cookbook hands over a task in your voice — profile this source, reconcile a change before the pull request. The blog is where we argue in ours.

Every post is anchored to something we can show you: a release we shipped and the problem that forced it, a claim about the category with its sources named, or an engineering method written out far enough that you can apply it to a stack that has nothing to do with Vibedata. Where the evidence is our own dogfooding, we say so. Posts land when one of those is ready rather than on a schedule.

One email for each new post — the same Proof, Provocation and Practice writing that is on this page, and nothing else. No product announcements, no event invitations, and no list sharing.