Types As Premature Optimization
summary
Argues static types are often premature optimization and can mislead when systems are chaotic, cites 70% of projects failed and a logic test where 90% answer wrong to show human reasoning limits. Recommends using Ruby as experimental clay (IRB, tests) and pushing strict types into small functional components like parsers or CLI code, uses parsing expression grammars and option semantics for nil, and points to Rubinius in Ruby as a real VM written in Ruby that runs in production.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:47We don't learn from failure
- 9:04Programming is a behavioral science
- 17:10Eight fallacies of programming
- 36:30General purpose
related talks
31mKnow Your Types - Bringing Static Types to Dynamic Languages
21mConsider Static Typing
41mWhat Developing With Ruby Can Teach Us About Developing Ruby
45mSoftly, softly typing
29mRoasting the Duck - A talk about Ruby and types
53mAn introduction to typed Ruby programming
56mOpening keynote by Matz: MythBuster
39mMatz Q&A