Core Principles Of API Design
Designing an API means providing an effective interface that helps your API’s consumers better understand, use and integrate with them while helping you maintain it effectively. APIs should be easy and intuitive to use while hard to misuse or abuse. Good API design is just like good product design. Two things matter above all else: empathy and context.
▶︎
Core Principles Of API Design - Part 2 (Class Design)
▶︎
Google & AWS Veteran: What Top Tier Software Architects Do Differently
▶︎
LiveCast: API Design Best Practices
▶︎
Zig 2026: No-AI Policy, $670K Foundation, Left GitHub & Why Zig Isn’t 1.0 - Andrew Kelley Explains
▶︎
System Design Explained: APIs, Databases, Caching, CDNs, Load Balancing & Production Infra
▶︎
Claude Architect: Multi-Agent Orchestration
▶︎
Message Brokers - Introduction
▶︎
Every Frontend Architecture Pattern Explained in 23 Minutes
▶︎
Unit Testing Strategy
▶︎
REST beyond the Obvious - API Design for ever Evolving Systems • Oliver Drotbohm • GOTO 2019
▶︎
Async-Await in C# 5 Part1
▶︎
ASP.NET Core Web API Action Result Types
▶︎
GraphQL, gRPC or REST? Resolving the API Developer's Dilemma - Rob Crowley
▶︎
Keynote: After the AI Hype – What’s Real, and What’s Next - Richard Campbell - 2026
▶︎
Never RESTing – RESTful API Best Practices using ASP.NET Web API - Spencer Schneidenbach
▶︎
Abstraction in Software Design
▶︎
Software architecture, human judgment, and AI's limits with Grady Booch
▶︎
System Design Course for Beginners
▶︎
Creator of C++: Bell Labs, Negative Overhead Abstraction, Mistakes | Bjarne Stroustrup
▶︎