Getting things done

I just read “The Duct Type Programmer” by Joel Spolsky. He proposes that getting things done is by far the most important thing when coding. Partly I agree. Yes, things must get done. There’s no win having a fancy architecture, great abstraction and so on if in the end you don’t have a product you can actually earn money with.
On the other hand I find it dangerous in interpreting “Getting things done” into don’t write tests or such. Yes, tests need time but tests can help you getting things done faster as well. Eric Burk commented that with a Twittch.