All issues
Ship Notes · SN #14·29 Mar
Designing the data model
The data model is the hardest thing to change later. Two notes on getting the foundation right early.
1. Model for how you read
Data is written once and read a thousand times. Shape it around the questions your app actually asks, and your queries stay simple as the product grows instead of turning into a maze of joins.
2. Migrations are forever
A schema change ships to production once and then lives with you for years. Keep migrations small, reversible, and boring — the riskiest ones are always the clever ones.
Previous issue
SN #13 — Auth you won't regret