Design Principles
summary
Argues that complexity needs concrete justification and offers a usable framework called a complexity budget that trades user sophistication and user care to decide when to add complexity. Demonstrates real tools and outcomes: LD preloads that let C programs transparently read zip files, an embedded Python2/Python3 bridge (pi3SO2), a 25‑line meta class enforcement that prevents test suites from skipping setup (which proves safer than a thousand‑line regex email checker), and notes CPython has 1,692 contributors.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:04Provocative code purpose
- 3:51Complexity risk in engineering
- 7:23Complexity competitive strategy
- 9:08When complexity justified
- 13:57Meta classes justified
- 20:17Complexity budgets framework
- 33:48Judgment over simplistic rules
- 34:30Question and answer session
