Ten Notes on Database Indexes

Abstract code gradient artwork

Security is mostly about saying no to defaults that were convenient in 2010. A boring deploy pipeline is a feature, not a lack of ambition. We measured first, and the bottleneck was not where anyone expected.

Context

Small pull requests get real reviews, large ones get approvals. Naming things well saved us more time than any framework migration. Latency percentiles tell a story that averages politely hide.

We wrote the migration twice: once to learn, once to ship. Feature flags are debt with an expiration date you must actually enforce.

A small example

We measured first, and the bottleneck was not where anyone expected. We wrote the migration twice: once to learn, once to ship. Small pull requests get real reviews, large ones get approvals. Every retry needs a budget, otherwise it is just a slower outage.

Feature flags are debt with an expiration date you must actually enforce. Small pull requests get real reviews, large ones get approvals.

The short version

A boring deploy pipeline is a feature, not a lack of ambition. Our on-call rotation improved the day we deleted half of the alerts. Most production incidents start as a small assumption nobody wrote down.

Latency percentiles tell a story that averages politely hide. Caches are easy to add and surprisingly hard to remove.

Our on-call rotation improved the day we deleted half of the alerts. A boring deploy pipeline is a feature, not a lack of ambition.

Comments

4 responses to “Ten Notes on Database Indexes”

  1. Small tip: the list at the end makes a great checklist.

  2. I tried this last week and can confirm it works.

  3. Chen W. Avatar
    Chen W.

    I’ve been doing it wrong for years, apparently. Thanks!

  4. Diego R. Avatar
    Diego R.

    Saving this for later, very practical.

Leave a Reply

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