News for hackers. Stuff that matters.

A comment on Ask HN: How to avoid over-engineering software design for future use cases?. Parent comment

Re:Ask HN: How to avoid over-engineering software design for... by theshrike79 on Wednesday June 24, 2020 @05:06AM (#23625780)
Exactly, in the time it would take me to write a proper TDD suite, I've written a skeleton of a product from end to end and can start iterating over it.

If you're working on a very specific box that has well defined, well known inputs and outputs then TDD is an excellent tool.

But for anything with a non-specific "We'd like to do X and display the result on Y" it just gets in the way.

[ Parent | on HN ]
Re:Ask HN: How to avoid over-engineering software design for... by 1337shadow on Wednesday June 24, 2020 @06:34AM (#23626325)
I'd TDD that "do X results in Y" and then add an end to end that that verifies that "Y is displayed", unless that code that displays Y is too trivial then an end to end test might not even be necessary.
[ Parent | on HN ]