Writing for Humans: Designing better software by keeping humanity in mind
summary
Argues that treating code as anthropomorphic entities improves design: objects behave like people, collaborate rather than suffer command-and-control calls, and honor boundaries. Uses a concrete example: ask the customer object for an address instead of reaching into an account to steal funds — ask the customer not the account. Advocates theater and actor metaphors so components are replaceable and can produce unexpected "magic," warns against deep taxonomic inheritance and urges focusing on behavior over categories, rooted in Ruby/XP culture.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:48Disclaimer
- 2:56What is software?
- 6:41Intellectual Complexity
- 7:19What is intelligence?
- 8:21Shifting Gears
- 9:24Tools & Techniques?
- 13:42Object Culture
- 18:49Think like an Object
- 21:23Declarative vs. Procedural
- 22:55Reinforcement
- 27:14Formalism
- 28:35Software Engineering
- 29:05Hermeneutics
- 29:52Semantics
- 30:37Metaphor
- 32:17Command and Control
- 34:34Replace Actors
- 35:01Magic
- 35:58Rigid Heirarchies
- 38:38Questions?
