Thinking in Terms of Resources Instead of Tables
One of the most significant mental shifts in API design is moving away from database-driven thinking. We often start by designing APIs around tables, schemas, or ORM models. While this approach may feel natural, it leads to brittle APIs that expose internal structure and limit evolution in the future.