|
|
|
|
|
by GenerocUsername
557 days ago
|
|
I blame bootcamp culture driven between 2010 and 2020. Students learning DRY on day 1 and then applying it to the max before intuitively understanding the problems DRY solves. I encounter people trying to establish standards and abstract patterns on the first pass of code... |
|
I put, for instance, TDD in the drills category. I don’t think you should live in TDD. nor do I think you should avoid TDD because someone said they thought it wasn’t a viable lifestyle choice. You should do it for a while every six months or a year to knock the cobwebs off and remind you what sort of tests you’re going to need and write code that complements good tests, rather than fighting them.
DRY is a bit more complex. I think DRY in unit and integration tests is a slow death. Tests should be DAMP because requirements change, and so do languages, frameworks and libraries. DAMP avoids the sunk cost fallacy which I’ve seen nerd snipe too many people. Test isn’t useful anymore? Just delete it. Or replace it. Boom, done.