
The failure that felt normal
A client's AI image feature failed on the same schedule every day since launch. The team called it normal and quietly lost every user who hit it.

A client's AI image feature failed on the same schedule every day since launch. The team called it normal and quietly lost every user who hit it.

How to predict what PostgreSQL would do with a query without running it: the statistics the planner reads and where an offline analyzer finds them.

Notes from a Tel Aviv meetup: why developer skepticism is mostly outdated, where the real concerns sit, and how adoption spreads without a mandate.

A hands-on Claude Code session: structuring prompts, holding context across a large codebase, and the habits that stop you burning tokens.

Once the layers and the instrumentation are in place, on-call changes. The practices that cut escalations from the rotation to the dev team.

Observability is not a tool you buy, it is code. How much of a production system is instrumentation, and what that costs in developer time.

An observability strategy built from the users a system serves: six layers from user experience down to infrastructure, and what each one answers.