TDD paralyzes me. I’m all for writing tests early in the process — especially in library code. But I can’t write them before I *play*. I need to write a shitty draft and play with the behavior to understand what I really want. Then rewrite guided by tests.
-
Show this thread
-
Replying to @dan_abramov @neil_killick
So, the problem is in “understand/define requirements” step. It is very hard to write tests before you understood the requirements
1 reply 0 retweets 1 like -
You can’t TDD something that has not enough clarity in requirements
1 reply 0 retweets 0 likes -
You can't code it without TDD either!
1 reply 0 retweets 0 likes -
Oh, you totally can. You would code “something” up. It likely would not be “it” though.
1 reply 0 retweets 1 like -
Replying to @SergeyIRL @chriswearshats and
Then you might just as well define that something using tests ;)
2 replies 0 retweets 1 like
Replying to @algo_luca @SergeyIRL and
At least you get to know the requirements you chose for your code.
9:00 AM - 19 Jan 2019
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at