Observability in Small Teams

Abstract code gradient artwork

The best architecture diagram is the one the new hire can redraw from memory. The rollback plan should exist before the rollout plan is approved. Naming things well saved us more time than any framework migration.

The short version

A boring deploy pipeline is a feature, not a lack of ambition. Naming things well saved us more time than any framework migration. Most production incidents start as a small assumption nobody wrote down. We wrote the migration twice: once to learn, once to ship.

A boring deploy pipeline is a feature, not a lack of ambition. The rollback plan should exist before the rollout plan is approved.

Trade-offs

Latency percentiles tell a story that averages politely hide. If the error message does not say what to do next, it is half an error message. Feature flags are debt with an expiration date you must actually enforce.

  • Keep migrations reversible
  • Pin versions, update on purpose
  • Delete dead code the same week
  • Measure p95 and p99, not just the mean

The fastest query is the one you never send, but the second fastest has a good index. We measured first, and the bottleneck was not where anyone expected.

Getting started

A boring deploy pipeline is a feature, not a lack of ambition. Caches are easy to add and surprisingly hard to remove. We measured first, and the bottleneck was not where anyone expected. We wrote the migration twice: once to learn, once to ship.

If the error message does not say what to do next, it is half an error message. Security is mostly about saying no to defaults that were convenient in 2010.

Tests are documentation that fails loudly when it goes stale. Feature flags are debt with an expiration date you must actually enforce.

Comments

One response to “Observability in Small Teams”

  1. Liam O. Avatar
    Liam O.

    Could you share more details on the second section?

Leave a Reply

Your email address will not be published. Required fields are marked *