|
|
|
|
|
by peterhunt
4925 days ago
|
|
TDD is good for some things, terrible for others. TDD's great when what you're working on is easy to test, like your data backend for your application. It'll vary based on your product of course, but in my experience I've found the frontend to be the big time sink in development. Using TDD for contemporary frontend development is, in my opinion, a big time sink since the cost/benefit ratio of frontend testing today is way too high. tl;dr use TDD for your backend (data model invariants) and hack your frontend as quickly as you can (on top of a decent frontend stack so you don't get that messy). |
|