Once in a while, I write longer form articles on technical subjects like APIs, Go, or Postgres:

• The Second Wave of the API-first Economy March 27, 2026

  APIs were meant to make the web programmable and interoperable. A combination of revenue chasing, security concern, and abuse reversed the trend for a decade as walls went up instead of down. Today, LLMs are changing the equation. People want agents that act on their behalf, and the services that ship APIs will have a decisive edge over those that don’t.

• Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go May 28, 2024

  Using a two-phase data load and render pattern to prevent N+1 queries in a generalized way. Especially useful in Go, but applicable in any language.

• The Notifier Pattern for Applications That Use Postgres May 5, 2024

  Maximizing Postgres connection economy by using a single connection per program to receive and distribute all listen/notify notifications.

I put short stream of consciousness thoughts into tiny posts called fragments:

• The special hell of Bolt, Europe's Uber clone July 15, 2025

  I don’t like this app.

• Occasionally injected clocks in Postgres June 29, 2025

  Using a coalescable parameter to stub time as necessary in tests, but otherwise use the shared database clock across all operations.

• Testing the graceful handling of request cancellation in Go, 499s June 19, 2025

  Using built-in net/http facilities to make sure that canceled requests are abandoned immediately to save time and resources.