Delicious Controversy: Docs & Tests
summary
Claims that pragmatism beats dogma: a codebase of 27,000 lines accumulates 16,000 lines of specs and huge maintenance cost; unit tests that mock internals create brittle coverage while well-scoped integration tests exercise the full stack and catch real breakage; use YARDlike docs to document public methods, move logic into services and presenters, use VCR for external calls, and reserve Capybara for a few critical user-flows so tests stay fast, readable, and actually prevent bugs.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:01DELICIOUS CONTROVERSY DOCS & TESTS
- 1:50LESSONS LEARNED
- 2:09CHAMPION PRACTICALITY
- 3:59SELF DOCUMENTING CODE IS A PIPE DREAM
- 5:56TESTS ARE TERRIBLE DOCUMENTATION
- 12:03UNIT TESTS ARE BAD TESTS • Too many lines of test code perline covered
- 14:12TDD CREATES BAD TESTS
- 16:40INTEGRATION TESTS TEST THE FULL STACK', CHECK THE RESULT
- 29:56SKINNY SKELETAL CONTROLLERS
