Unfactoring From Patterns
summary
Claims that deliberately making well-factored Ruby code hard to read secures the original author’s job by making others avoid it, and shows a practical recipe: write tests to preserve behavior then apply small iterative transforms that inline duplicated code, change iterators, introduce off‑by‑one quirks, abuse send/eval/globals, and obfuscate names with Pig Latin. The demo forks Rails, scaffolds an “Augble” blog, unfactors views and controllers but keeps features working, proving the technique preserves behavior while wrecking maintainability.
AI-written summary · about
chapters (6)
- 0:00Introduction to unfactoring
- 2:27Core principles of unfactor
- 5:52Case study analysis
- 8:18Live demo: Unfactoring Rails
- 10:48Advanced unfactoring tactics
- 17:36Audience Q&A and wrap up
