Pre-factoring: Getting it (Closer to) Right the First Time
summary
Claims that a little upfront design prevents long-term tech debt and that refactoring must be baked into the process. Case study builds panometer from command-line tools (Society gem fukuzatsu reek), a job runner Panda pounce, a Rails JSON API and D3 frontend, and ends with painfully slow recursive queries and a 200,000-character JSON measurement model requiring major rework. Advice: design for reads, budget modest architecture work, and treat deadlines as milestones.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:10Architecture
- 4:20Case Study
- 9:15Why do we do this
- 12:27Acronyms
- 14:14Legacy
- 18:37Conclusion
