Explains why Azure Functions with HTTP triggers are not ideal for building full web APIs and should be used for reactive, message-based logic instead.
Explains opaque return types in Swift 5.1, covering their syntax, benefits for API encapsulation, and differences from protocol return types.
PSPDFKit shares insights on maintaining a large, cross-platform SDK, focusing on API evolution, proposal-based development, and long-term code maintainability.
A React team member shares personal strategies for coping with stress and feedback after major project releases like React Hooks.
A guide to implementing data validation and proper error response handling for REST APIs, covering validation rules and the Problem Details standard.
Explains why certain React APIs like React.memo are not Hooks, focusing on composition and debugging constraints.
Introduces the 'Bug-O' notation, a metric for how API design affects debugging speed as a codebase grows.
Explains the rationale behind React Hooks' reliance on call order and how it enables features like multiple state variables.
Explores the importance of designing APIs that are not just readable but also optimized for how code evolves and changes over time.
A tutorial on building a GraphQL server with Node.js, comparing it to REST APIs and demonstrating how to reduce over-fetching.
A developer shares ten essential principles for building and managing scalable software platforms, based on lessons from running platforms at scale.
Argues that method chaining should be a core language operator, analyzing its problems in JavaScript/jQuery and proposing a built-in solution.
A quick guide to implementing the Facade design pattern in Swift, demonstrating how to simplify complex subsystems with a clean API.
A Swift developer shares a better approach to naming protocols for testability, focusing on behavior over types.
A guide to implementing custom model binders in ASP.NET Core to handle multipart requests containing both JSON data and file uploads.
Explains the software design principle 'Make impossible states impossible' to improve UI component APIs and state management.
Explores the modular architecture of JUnit 5, detailing its Jupiter, Vintage, and Platform sub-projects and the design rationale.
Explores the advantages of using RPC over HTTP for communication between microservices, focusing on simplicity and avoiding RESTful complexity.
A developer explores a hacky React solution for handling errors in a custom i18n library's 'sorta-curried' API.
Argues against using nested routes in RESTful API design, advocating for simpler, single-resource endpoints with query parameters.
