· 1 min
The Data Act turns one on September 12. Check your contracts first.
September 12 marks a year of regulated cloud switching. A pre-anniversary note on what to audit before the think pieces arrive.
Dispatches
24 entries
· 1 min
Postgres 19 Beta 3 ships alongside 28 security fixes for the stable line
Third beta on August 13, 28 vulnerabilities patched across the stable branches, and Postgres 14 gets an end-of-life date. GA is weeks out.
· 1 min
In praise of beta season
An editorial on why a database beta deserves more of your attention than most general-availability launches.
· 3 min
Moonshot published Kimi K3 open weights. The license carries the model's own name.
2.8 trillion total parameters, 104 billion active per token, a million-token context window, and terms written by the lab. The license is the story.
· 1 min
GitHub started grading its own homework in public
The June availability report keeps the transparency section, admits a month-long deliberate pause, and reports a missed 50% target with no new date attached. More of this, everywhere.
· 1 min
What the desk read this week
The first of an occasional micro-column, three links and the reason each earned its place.
· 1 min
The mid-year scorecard
Five dispatches revisited, three verdicts upheld, one pending, one wrong in an instructive direction.
· 1 min
OVH wrote the letter the big three are still drafting
European cloud pricing rises 5 to 10 percent this year, openly. The hyperscalers buy from the same factories and have said nothing. Both facts are information.
· 1 min
The AI buildout, read as a balance sheet
The hyperscalers are racing to pour concrete, the analysts are racing to rank them, and the number that matters is the one nobody reports quarterly.
· 1 min
Six months after the agent keynotes, an accounting
re:Invent promised agentic development at scale. Half a year on, what shipped, what stalled, and the safeguard that tells you where this settles.
· 1 min
Postgres 19 enters beta on schedule, as always
Beta 1 on June 4, GA around autumn. The most dependable release calendar in infrastructure does it again.
· 1 min
An incident review that changes nothing was theater
A short editorial on the incident review's only real deliverable, occasioned by a season of reading them.
· 1 min
The internet keeps breaking in the same three ways
A winter and spring of incidents, one editorial. Config is the trigger, routing is the amplifier, concentration is the blast radius.
· 1 min
The chillers failed in Northern Virginia
May 7 and 8, multiple cooling units down at once, one availability zone thermally offline. The dependency map did the rest.
· 1 min
Linux 7.0 shipped. The distributions inherit it immediately.
April 12, on schedule, called solid progress by its own author. The LTS timing is the consequential part.
· 1 min
Weekend read: a trolley problem you can actually play
GroundNet is a playable version of last year's agentic misalignment research. Twenty minutes, one uncomfortable conclusion.
· 1 min
The thirty-year argument ended in a driver directory
An editorial on how the kernel actually decided the Rust question, and why big technical arguments end administratively, not rhetorically.
· 1 min
Linux 7.0 is in release candidates, and Rust is staying
Torvalds confirmed the version jump in February; rc5 landed late March. The number is cosmetic. The language decision underneath it is not.
· 2 min
The practitioner notebook is beating the press release
An editorial on where the best infrastructure writing actually lives now, with exhibits, and what vendors could learn from a homelab.
· 1 min
Ingress NGINX is retiring. Half of Kubernetes did not get the memo.
Best-effort maintenance ends this month, then the archive. The replacement has been ready for years, which is exactly why nobody moved.
· 1 min
The postmortem is the best genre in engineering writing
An editorial in praise of the documents this winter keeps producing, and the tell that separates real ones from theater.
· 1 min
Cloudflare leaked BGP prefixes from Miami. The internet noticed.
A February 20 routing incident took BYOIP customers off the map. The cause was an automated policy change, which is the year's refrain.
· 1 min
Amazon says an AI caused a December incident. The fix is a form.
A February disclosure, a production change initiated by an AI system, and the oldest safeguard in engineering applied to the newest actor.
· 1 min
Dispatch zero
What this wire is for, what it will not do, and the one promise that makes the rest enforceable.