Collaboration between roles.
WHAT DEVELOPERS OPTIMISE FOR
Delivering features.
WHAT ADMINISTRATORS OPTIMISE FOR
Stability, performance and recoverability.
WHY THAT TENSION IS HEALTHY
Each catches what the other misses.
WHAT TO REVIEW BEFORE A SCHEMA CHANGE REACHES PRODUCTION
Types and lengths Indexes for the queries it will serve Constraints How long the change takes on real data Whether it can be rolled back
WHAT TO ASK ABOUT ANY NEW TABLE
How large will it get How will it be queried What must be unique What must exist
WHY THE QUERY QUESTION MATTERS MOST
Indexes follow from queries, not from the table alone.
WHAT TO OFFER RATHER THAN REFUSE
An alternative that achieves the same result safely.
WHY
Blocking without offering produces workarounds nobody reviews.
WHAT TO PROVIDE DEVELOPERS
A realistic dataset to test against Visibility of slow queries from their own code Guidance written down
WHY A REALISTIC DATASET
Nothing else surfaces performance problems before release.
WHAT TO AGREE
That migrations are tested against production-sized data.
WHAT TO AVOID
Discovering a schema change at deployment time.
