I/O 2026 and the assistant that lives in everything
More model, more surfaces, and a search product that keeps changing what the web is for.
page 3
older dispatches from the README archive.
Error messages are a user interface
The message someone reads at their worst moment gets less design attention than a button. Here's what a good one contains.
Build 2026 and the platform that keeps absorbing
Agent infrastructure at the OS layer, more of the developer stack open-sourced, and a strategy that has not changed in a decade.
Naming things: the actual rules
It is one of the two hard problems and it is treated as a matter of taste. It isn't. Here are the rules that hold.
Hiring juniors in 2026
The entry-level pipeline is breaking in a way that will be expensive in five years. Some of the fixes are cheap.
Search is hard and you should probably not build it
Relevance ranking is a specialist discipline. Here's the decision tree, and what to do at each level.
Migrations that don't wake anyone up
Data migrations at scale, done in a way that is reversible at every step and boring in the middle.
The three kinds of technical debt
Deliberate, accidental, and structural. They need completely different responses and everyone calls them the same thing.
Accessibility is a testing problem
Most accessibility failures are mechanical and catchable. Treating it as a specialist concern is why it doesn't get fixed.
The Cyber Resilience Act and the unpaid maintainer
Europe is about to regulate software security across the whole product lifecycle. Open source is mostly carved out, and mostly is doing a lot of work.
The retrieval question, revisited
Context windows kept growing and retrieval did not die. It changed shape. Where the line actually sits now.
The API versioning decision
URL versions, header versions, or no versions. Each is a bet on how your consumers behave, and one of them is usually wrong.
You still do not need Kubernetes
It's excellent software solving a real problem that most teams do not have. The honest threshold, and what to do below it.
Observability costs more than the thing it observes
At some point your telemetry bill exceeded your compute bill and nobody noticed. Here's how to fix it without going blind.
Infrastructure as code, ten years of lessons
State files, drift, modules that became frameworks, and the one practice that separates teams that like their IaC from teams that don't.
Rate limiting: the four algorithms and when each is wrong
Token bucket, leaky bucket, fixed window, sliding window. They fail differently and the differences matter.
Node 26 and the build step that finally disappeared
Type stripping, a mature test runner, and a standard library that absorbed the ecosystem. You can ship TypeScript with no toolchain.
The joke RFCs are the best documentation
RFC 1149, RFC 2324, and why the internet's funniest specifications are also its clearest.
Q1 2026, in one page
Regulatory deadlines, a linker change, and a quarter where the interesting news was mostly infrastructure.
The database you should have chosen
Postgres. That's the article. Here's the longer version, including the cases where it's wrong.