Keynote: Writing Software
summary
Argues that test-driven design often degrades architecture by forcing needless dependency injection, shows Rails examples where unit tests pass yet Basecamp loses data, and prefers clarity over tests and coarse-grained regression checks to chasing coverage, speed, and ratios. Demonstrates concrete fixes in Ruby on Rails and ActiveRecord, advocates reading and rewriting code, deleting needless concepts, and treating software as writing: rewrite drafts for simplicity rather than sprinkling patterns to hide poor design.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 4:50First computer
- 9:48BBS
- 12:34We are not programmers
- 14:23Information system development has little to do with science
- 16:24What is programming
- 17:27Law of Demeter
- 19:22Pseudoscience
- 19:52Diet Schemes
- 21:51Overweight
- 23:06Imposter Plexus
- 23:39The Ten Commandments
- 24:12TDD
- 26:51Code
- 29:06Controller
- 30:52Crate
- 31:26ActiveRecord
- 31:57Unit Testing
- 34:56Fixture Testing
- 36:04Test Coverage
- 42:03Cost vs Value
- 42:55Regression Testing
- 44:01TDD Kent Beck
- 45:01David HeinemeierHansson
- 46:44Software Engineers
- 47:16Writing
- 49:34Clarity
- 50:35Develop an eye
- 53:18Read a lot of code
- 54:03Is it with code
- 55:36Readability
- 57:21Length
- 58:02First Draft
