Lightning Talk: Effective APIs in Practice in C++
summary
Five quick, actionable claims: five concrete tips that change APIs rather than restate principles. Better names reduce ambiguity, strong types force callers to construct the right units so wrong calls fail at compile time, and replacing swappable booleans with a direction/configuration class makes intent explicit. Move multi‑step setup into constructors to avoid surprising side effects, and follow a clang‑tidy rule to detect risky parameter patterns so the examples actually prevent bugs rather than just documenting them.
AI-written summary · about
chapters (4)
related talks
30mFrom futons to functions: the principles of good API design
27mLightning Talks - Day 1
01h 01mGrowing Pains: Lessons from seeing C++ codebases mature
24mProviding a childcare service for your API
36mEverything is an API
11m⚡Lightning Talk: No More If-Else Soup: Scalable Feature Flag Architecture With Design Patterns
01h 00mDesign Idioms from an Alternate Universe
01h 00mBack to the basics: Namespaces 101