Infrastructure and developer tooling · a publication

about.json

147posts published
202glossary terms defined
8standing beats

What this is

A publication about infrastructure, developer tooling, and the practical edges of shipping software. Every post is researched, drafted and fact-checked by an agent pipeline, then read by a human who decides whether it goes out

How a post gets made

Six stages, each one able to send the piece backwards. A defect caught early costs a replan. The same defect caught at the end costs a rewrite

  1. 01
    Demand

    Topic

    Reddit threads and search demand are mined for questions people are already asking, then ranked. Nothing gets written because it sounded clever

  2. 02
    Legwork

    Research

    Parallel agents run searches, fetch primary sources and measure things firsthand. Anything load-bearing has to trace back to something checkable

  3. 03
    Structure

    Skeleton

    The piece is fitted to a genre skeleton before a sentence is drafted, so the argument has a shape it has to earn

  4. 04
    Draft

    Writing

    One pass, written against the locked skeleton and the evidence gathered in stage two

  5. 05
    Panel

    Verification

    A review panel attacks the draft on separate lenses — claim accuracy, dead links, tone drift, whether the strongest objection survives the article’s own text

  6. 06
    Gate

    Editor

    A human reads it and decides whether it ships. Nothing reaches this page without that step

Editorial standards

What gets covered

  • Infrastructure, developer tooling, and the practical edges of shipping software
  • Work done firsthand, wherever the topic allows it. Measured beats cited, cited beats assumed
  • No sponsored placements, no affiliate links, no paid inclusion of any kind

The accuracy bar

  • Every factual claim traces to a source that was actually opened, not a source that merely exists
  • Every outbound link is probed live before publish. Dead ones do not ship
  • Numbers carry their method. A benchmark without the conditions that produced it is not a number

Corrections

  • Errors get fixed in place and the change is stated, rather than quietly rewritten
  • Posts that age badly get a note rather than a deletion
  • Corrections can be sent through the contact page and are read by a person

Author of record

Edited by Andrew Rayner, who is accountable for everything published here regardless of what drafted it

Receipts

Each post is stored with the manifest that produced it — the brief it was written against, the artifacts it used, and what the verification panel checked

119 of 147

posts carry a full build manifest

Unbroken since May 2026. Earlier posts predate the pipeline and are kept as they were rather than backfilled with a manifest they never had

Read the corpus →
The feed →Glossary →Tips and corrections →RSS →

rizz.dev · edited in Houston, TX