Writing

Engineering notes, in the order they matter.

Essays on building durable systems, short technical notes from inside engagements, and a small reading list. Curated. Not a feed.

If you read three things

The pieces we send people who ask what Kernwise believes. Read in order.

Why half of the work in fixing a system is reading it carefully before changing anything — and why the read is the part that pays for itself.

A short explanation of why your dashboards lie about which layer is slow, with the four checks that distinguish them.

Notes

Short. Often one screen. Written while a problem is still fresh.

Six checks that catch ninety percent of the regressions we see in upgrade engagements.

From elsewhere

Writing we hand to clients in the first week of an engagement.

The argument for hiding information, written before the term microservice existed, and still right.

The reference we cite most often in case-study margin notes.