I wrote some opinions on this in other thread: http://news.ycombinator.com/item?id=46526 http://news.ycombinator.com/item?id=46526 Unless your software will k

I wrote some opinions on this in other thread: http://news.ycombinator.com/item?id=46526 http://news.ycombinator.com/item?id=46526 Unless your software will kill people if it fails or something, my advice is: observe what proportion of your development time you spend debugging. If it's one half or more, unit testing would probably benefit you. If it's significantly less than 50%, then you're probably better off riding bareback, because writing and updating those tests will take at least half of your time. The problem I see with the "you'll test anyway, you may just as well automate it" argument is that unit tests are no substitute for testing with real users.