Don't demolish the wrong house

As developers we spend a lot of time coding versus nailing down requirements. Probably 20-1 or higher if you're a developer in the trenches getting handed specs from higher up, maybe 10-1 if you're managing the development top to bottom. When something gets built wrong a lot of times it's a waste of a good number of hours of development time that could probably have been fixed with a couple more minutes diving into the client's head a little more deeply. I need to pinch myself occasionally to remind myself to clarify issues ahead of time rather that after the fact. The main problem is developing is fun. Nailing down specs during client meetings and calls is not.

Just something that popped into my head again (talked about previously in Specs: the Consultant's McGuffin) after reading the Texas Woman's House Demolished By Mistake on the Consumerist.  I'm guessing demolishing a house isn't easy. Double checking that you have the right house listed on the job sheet is a lot less effort in comparison even if it's not quite as fun as just firing up the bulldozer and taking down the first residence you see.