Notes on building software, scaling teams, and shipping product.

Postgres 14 receives its final fix on 12 November. Postgres 19's GA has slipped to late October at best. Upgrading to a two-week-old major release to escape an EOL date is the wrong trade.

EFRAG published the revised ESRS datapoint list in two versions — one of them a mapping back to the 2023 standard. That mapping is a migration file, and most compliance products cannot run it.

Anthropic's commerce blueprint splits its guardrails into two tables: what the code enforces, and what the prompt merely asks. Only one holds on any model. Here is how to audit your own agent.

Everyone read the 2026-07-28 MCP spec as a scalability win. It is a governance bill — and the two headers it made mandatory are the most useful thing in it. Here is what to fix.

84% of developers say AI made them faster. Only 20% of companies can prove it. The saved hours are real — they are sitting in your review queue, and you can measure that today for free.

The agent never escaped the sandbox. It used the internet access it was handed. Filesystem isolation is not containment — egress is the boundary, and here is how to tier it and audit it this week.

Every Postgres 19 roundup leads with REPACK CONCURRENTLY. For a shared-schema multi-tenant SaaS it is the wrong feature — and the one that matters ships disabled by default.

Next.js now ships pre-announced monthly security patches — four high-severity CVEs in the first batch. The exposure triage and patch runbook I run to absorb them with no security hire.
.jpg%3F2026-07-29T09%253A59%253A53.643Z&w=3840&q=100)
"Build vs. buy" is the wrong question for an AI feature. Split it into three layers — model, orchestration, surface — and a five-question test tells you which one to build and which to rent.

Adding a second agent isn't an upgrade — it's a 3–10x token bill and a new failure mode. When a multi-agent system actually earns its cost, and the control layer I put around every spawn.
.jpg%3F2026-07-14T18%253A30%253A14.918Z&w=3840&q=100)
The industry turned platform engineering into a hiring decision. It isn't. The minimum viable platform I run on Keaz across twelve services — no platform team — and when to finally hire one.

A webhook handler that does real work inline is a data-loss bug waiting for a traffic spike. The durable pattern I run on Keaz — persist, queue, process idempotently — and where it breaks.