Why are TDD 'Spikes' called 'Spikes?

Question

The test driven development guys refer to a quick, exploratory, investigation that involves coding something up to see if it works, a spike.

Any ideas why they came up with that word?

Update: The coinage by Kent Beck looks like the 'original' one to me, although his usage of the word doesn't make much sense in my opinion. Coding up a quick test is 'putting a spike through the project'?

Interestingly, it seems he stopped using the term because it conjured up various meanings to different people - see below for evidence!

Answer 1

Ward Cunningham writes on WardsWiki (referring to Kent Beck):

I would often ask Kent, "What is the simplest thing we can program that will convince us we are on the right track?" Such stepping outside the difficulties at hand often led us to simpler and more compelling solutions. Kent dubbed this a Spike. I found the practice particularly useful while maintaining large frameworks.

Kent Beck writes in Guide to Better Smalltalk:

Sometimes I call this a "spike," because we are driving a spike through the entire design. [...] Because people variously associate "spike" with volleyball, railroads, or dogs, I have begun using "architectural prototype" to describe this implementation.