News for hackers. Stuff that matters.
Re:When you shouldn't bother unit testing by nahname on Friday May 17, 2013 @09:44AM (#5724255)
I've found one simple rule works well for the teams I have been on. If you can afford to re-write the entire application from scratch (considering time and money) then you can afford to skip unit testing.

On a side note. You will never learn TDD from a video. If you want to learn TDD, get very familiar with testing in general, pick a domain you are comfortable with and then force yourself to write tests for everything before code. Repeat 2-3 times and you will be better at TDD than 80% of the people who are presenting on it.

Re:When you shouldn't bother unit testing by seren on Friday May 17, 2013 @10:14AM (#5724445)
Do you think it makes sense to try to learn TDD on a language you don't know ? So let's say I want to pick Go (as a hobby, not for a particular professional need in the short term), would it make sense to try doing some TDD on my first smallish applications ?
Re:When you shouldn't bother unit testing by nahname on Friday May 17, 2013 @10:52AM (#5724666)
I don't think there is anytime not to try to learn it. It will be harder the more unfamiliar you are with everything else (language, libraries, domain, etc...)
Re:When you shouldn't bother unit testing by Noughmad on Friday May 17, 2013 @10:42AM (#5724614)
Why not? It's nice to make a fresh start, as with a new language you will not fall into your old habits so easily.