We started the blog after noticing that our best internal postmortems were more useful than most of the articles we read. They had the actual query, the actual stack trace and the honest bit about the first wrong guess. Public writing tends to sand those parts off. We try to keep them.

Every post goes through one round of review by another author. The reviewer runs the code, checks the commands against a clean environment and asks the annoying questions. If a snippet does not run, the post does not ship.

The companies and products in our examples are made up, and so are the numbers when they need to be. The techniques are not. Everything here is something one of us used on a real system, usually after it broke.

No sponsors, no affiliate links, no ads. The site is static, the RSS feed is full text, and the newsletter is a plain email when a new post is published.

authors with pagers
4
posts since 2026
112
sponsored posts
0

The writers

Portrait of Ilse Brandt (illustration)

Lisbon, Portugal

Ilse Brandt

Database engineer · Lisbon, Portugal

Ilse looks after Postgres for a payments team: migrations, indexes, vacuum and the queries nobody wants to own. She writes about EXPLAIN output and schema changes that do not take the site down.

Portrait of Tobi Okeke (illustration)

Lagos, Nigeria

Tobi Okeke

Node.js platform engineer · Lagos, Nigeria

Tobi runs the Node services behind an events API and has read more heap snapshots than he would like. He writes about memory, the event loop and the runtime flags that save a release.

Portrait of Marek Dvořák (illustration)

Brno, Czechia

Marek Dvořák

Site reliability engineer · Brno, Czechia

Marek writes Go for the infrastructure side: proxies, workers and the retry logic in between. His posts cover profiling, backoff and what happens to a system when a dependency goes slow instead of down.

Portrait of Hana Sato (illustration)

Osaka, Japan

Hana Sato

Developer tooling lead · Osaka, Japan

Hana owns CI, the monorepo and the test suite at a mid-sized SaaS team. She writes about fast builds, flaky tests, feature flags and the small internal tools that are cheaper than a vendor.

Live demo · Green Build Gazette— View template →