My Dog Taught Me to Code
summary
Thirty concrete claims boiled into 30 Reader's Digest style rules including a single design metric — good design is easier to change — and concrete tools: Ruby and Rails examples (a 490‑char line rewritten, a string‑concatenation bug exposed by layout), Elixir service patterns that copy input hashes, MapReduce/divide‑and‑conquer fixes, and heavy gem dependency pain (124 gems, ~511 lock entries) that gets resolved by inlining three lines of library code. Deleting most of thousands of tests except money tests speeds development; accessible‑first UI changes simplify features and work.
AI-written summary · about
chapters (27)
- 0:00Intro
- 14:21Patterns
- 15:32Avoid Inheritance
- 16:52Postures Law
- 19:21Listen to the Code
- 20:11Data vs Classes
- 21:13Stop Designing with Classes
- 22:04Delete the Tests
- 24:05Consistency is Key
- 24:42Divide Conquer
- 26:16Large Systems vs Small Systems
- 27:04Dont write monolithic systems
- 28:02Dependencies
- 29:16Be Joyful
- 31:00Never Call
- 31:32Accessible First
- 34:00Data Structures
- 34:36Algorithms
- 35:50Books
- 36:13More Things Change
- 36:27More Things Stay the Same
- 39:38Being Nice
- 41:20Flow State
- 44:18Open Source
- 45:04Pay Back
- 45:57I Love Ruby
- 47:13The Future
related talks
30mBringing UX to Your Code
35mAmelia Bedelia Learns to Code
30mThe Ten Commandments of the Ruby Programmer
01h 01mKeynote: Writing Software
25mAmelia Bedelia Learns to Code
31mAn Optimistic Proposal for Making Horrible Code... Bearable
34mCode Spelunking: teach yourself how Rails works
29mA Tale at Any Scale