Tag
problem-details
- Sep 30, 2026 Error Contracts: Problem Details, Stable Codes, and Retry Semantics How to design an error payload that machines can branch on and humans can act on, and why retryability belongs in the contract rather than in the status code alone. software architecture
- Feb 7, 2024 Stable Error Codes as Documentation Identifiers Human-readable messages change with wording and locale. A code that never changes, is never reused, and is documented once is what lets callers and support engineers agree on which failure occurred. software engineering