Recovering from Enterprise
summary
Argues that Java = Lego (11,000 public classes, 46 collection choices) while Ruby = Play‑Doh (≈1,400 classes, ~6 collection types), and shows concrete failures: Copeland (YAML loader plus optional XML hook) becomes over‑engineered, Needle’s pipeline API explodes into "component soup," and using Needle inside net-ssh complicates rather than simplifies. Recommends small opinionated DSLs, avoid static config and DI frameworks in Ruby, apply YAGNI and code just‑in‑time.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:09LEGO
- 9:46Ruby
- 12:19Exhibit A
- 16:56nic Class Lookup
- 17:42Exhibit C
- 23:33Small API's
- 26:29Exhibit E
- 31:49sons Learned
- 34:34Links
related talks
30mRuby Techniques by Example
18m"Good Enough"
01h 00mClosing Keynote: After a Decade, Still a Rubyist
38mProgramming Language Stereotypes
33mFrom Enterprise Architecture to Software Design - Critical Thinking
45mToward a Design for Ruby
01h 01mGuide to Destroying Codebases the Demise of Clever Code
27m“Good Enough” Architecture Part 2