Topic guide · 02

Performance

Performance is not a score; it is the delay between a person's intent and the system's response. This guide follows three places that delay hides: the tail, the layout, and the build.

3 essays 15 min read Curated path

The argument

Start here
  1. Averages hide the failure

    A p50 can look healthy while one tenant waits seconds. Measure the population, read the p95, and fix the tail instead of the average.

  2. Layout shift is a missing reservation

    The browser moves content because nobody told it how much space to reserve. Make that decision before paint, not after the layout has already shifted.

  3. Build time is user-facing too

    Every minute in CI is a minute the team cannot ship. Treat pipeline latency as a product metric, with users, a failure mode, and a budget.

All essays in this guide

Tag archive →
Jun 16, 2026 A Field Guide to Slow APIs Your API is not slow everywhere. It is slow for one query, one tenant, one hour. Find that hour, read the p95, and fix the tail instead of the average. performance · engineering 5 min Sep 02, 2026 Cumulative Layout Shift, in Practice Layout shift is rarely a CSS bug. It is a missing decision about who reserves space, made late in the rendering pipeline. performance · engineering 5 min Oct 06, 2026 Your Build Pipeline Is a Product If your pipeline has users, it deserves a product manager. Treat build time as a feature, flakiness as churn, and every red build as a support ticket. devops · engineering 5 min

Continue with Architecture

Open guide →

Performance work eventually runs into architecture: the boundary that forces an extra round trip, the dependency that cannot be cached, the abstraction that hides a query. The Architecture guide starts where those decisions are made.

Search essays