Simple Questions Should Have Simple Answers
summary
Argument: simple questions get simple and easy answers by adding small, well‑scoped APIs. Evidence: Perl 5i (Perl 5 improved) adds methods like touch_path and is_number so “touch a file” and “is this a number” become one call instead of many modules, manual utime calls and error branches. Tools: CPAN, path objects, caching and a planned backwards‑incompatibility release strategy. Surprise: a ~50‑module dependency tree is tolerable if installation is distilled to a cut‑and‑paste setup and if teams make being wrong cheap.
AI-written summary · about
chapters (40)
- 0:00Intro
- 0:41How do I touch a file
- 2:31Python
- 3:35Simple Question Simple Answer
- 4:20Simple Made Easy
- 4:52Simple vs Complex
- 6:33Easy
- 7:31Simple
- 8:16Its not necessarily simple
- 9:53Simple questions have simple answers
- 10:46Consequences
- 11:16Corollaries
- 12:54Design Optimism
- 13:13Unpacking Arguments
- 13:46Module Pro Libraries
- 14:24Profi Metric
- 15:01Cut Paste
- 15:31Number Method
- 17:07Default
- 18:13Backdoors
- 19:10Developer centric
- 21:37Make being wrong cheap
- 22:29Predicting the future
- 23:01Backward compatibility
- 24:39Expanding
- 25:44Finding the Simple Problem
- 26:51Considering the Problem
- 30:32Find the Problem in a Bad Solution
- 31:32Why
- 31:44The Five Wise
- 33:37Getting tes
- 34:48What would Star Trek do
- 35:32Google Now
- 36:59Tripit
- 38:29Memory Allocation
- 39:15Step Zero
- 46:10Quick Stop Words
- 47:22Design of Everyday Things
- 48:01Civil Made Easy
- 48:17Sloth
