Conversations vs. Laws
summary
Argues that Ruby treats type is abstract and class is concrete, not as a formal contract, cites the deprecated type method and the Java vs Ruby array debate about one Array doing lists stacks matrices, and notes real-world collisions like a duplicate "file system" library on RubyForge. Points to practices that actually work: unit tests and agile feedback loops, Rubinius and JRuby efforts, Toyota Kaizen as a decision model, and the web’s messy dependency reality — Ruby is a low contract environment.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:10Dynamic language community
- 1:29Broader ideas
- 2:02No types
- 4:10Trees
- 5:09Biology
- 7:05Species
- 7:30Ring Species
- 8:20Computing and Society
- 8:59The Curse of Ham
- 10:18Disclaimer
- 11:36DNA Testing
- 12:47Are Types Real
- 13:11Marriage
- 13:26Terri Schiavo
- 13:44Conversation
- 14:35Ruby vs Java
- 16:19Dynamic Language
- 17:51Laws
- 19:22Restorative Justice
- 21:57Ruby
- 23:59Java
- 25:20The Web
- 28:25Robotics vs Computer Science
- 29:23Jaron Lanier
- 43:56Questions
- 48:14Chain Forces
- 59:03Java Architects
