Re:Test driven development at Transloadit
by loewenskind on Friday October 29, 2010 @10:52AM
(#1847484)
>I find it a crime to write code that I know won't work, just to write a more comprehensive test and then rewriting it, wasting a ton of time.
I don't remember this being in TDD. Could you expand on this? I remember the rule that you write the simplest code that will pass the test and no more, but I don't recall that causing any rewrite per se.
Re:Test driven development at Transloadit
by felixge on Thursday October 28, 2010 @11:25AM
(#1843231)
Statically checked language have certain advantages and disadvantages.
As far as speeding up the process goes, I always have test and code in a vim splitscreen, along with a keybinding that allows me to run a test from within vim. It takes me << 1 second to witch between the two and execute a test.
Thats one of the things that turned me of TDD for good - I find it a crime to write code that I know won't work, just to write a more comprehensive test and then rewriting it, wasting a ton of time.
The other was constantly switching between code/test/code - even if it only takes 5 seconds, that essentially means that each statement now costs 10 seconds(time to confirm the test failed plus time to confirm that it has now passed) + the time to write the test.
This is also the reason I tend to stick to statically checked languages.