Lightning Talk: The Most Important Design Guideline
summary
Central claim: make the right thing easy to do and the wrong thing difficult to do. Concrete examples show how that plays out: prefer APIs that return ownership rather than raw pointers, convert a C ANARI set-parameter call that memcpys from void* into a C++ wrapper that uses type traits and static_assert to pick the correct enum and stop misuse at compile time, and treat build and runtime interfaces the same way so common errors become hard and correct usage becomes obvious.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:14The Most Important Design Guideline
- 1:05Architecture and Structure of Your Project
- 1:38The Best Design Guideline Is To Make the Right Thing Easy To Do and the Wrong Thing Difficult To Do
- 2:09Comparative Heuristic
- 2:30Why Do We Care about Interfaces
- 3:05Memory Ownership
