A Simple Mental Model for API Error Handling

Instead of a generic try/catch everywhere, I've found it useful to model API errors as one of three types: not-found, validation, and unexpected. Each gets handled differently in the UI, and the distinction makes error states much easier to reason about.