Wicked Bad Ruby
summary
Claim: no such thing as bad code — quality is decided by concrete outcomes, tradeoffs and expectations, not prettiness. Examples: a real Rails controller allegedly over 3000 lines, a stack with 60–80 gems, a startup product (Splice) using Rails front end and Go backend, an experimental project that hits Hacker News with low test coverage. Covers practical rules (define expected outcome, pick a solution, implement, refactor continuously), TDD/BSD limits, and how to communicate team values.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:57define expected outcome
- 7:22evaluate solutions
- 7:37implement
- 10:19hard to understand
- 11:11You're doing it wrong
- 20:16communicate!
