# I never have enough time to write the tests, once I’ve finished the
main functionality.=> you shouldn’t be a programmer in that case, your code will be full of bugs

# Testing isn’t my job, because it’s QA’s job to make sure I do quality work. => Test is code and you’re being paid to code. Testing is part of the development cycle. Best Practice!

# Unit tests don’t help me, because my code always works perfectly when I add new features.=> code isn’t yours… there’s an 80% chance of getting legacy code => what happens if you modify that code or add new features?

# There’s no need to test drive my code, because the design handed to me by the architect covers every possibility => what’s your architect?? Eric Evans??

# Running the tests is a pain, because it takes too long to scan through => Have you ever heard about Continuous Integration?

# Running the tests takes too long, because reloading the database
and restarting the app server between tests takes forever => same as above

# TDD is just a fad, and it’s completely unnecessary anyhow since projects always succeeded before => projects were a lot simplier, and the idea is to complete things with less efort that what we’ve done in the past

# Unit tests don’t help me, because my code works perfectly the first time. That’s not true… are you coding beans? have you tried c++???

# I don’t like TDD, because I enjoy the hours I spend in my
debugger => but your boss don’t, and it’s paying for your time

Has thinking moved on?
Any newer blogs you would recommend?

BTW, I should mention that the format of this was inspired by:

http://www.blueskyonmars.com/archives/2004/02/29/12_reasons_gay_marriage_will_ruin_society_not.html