Comments on: Throw Away Code (aka Spike Solution) http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/ Thoughts on .NET, Agile and beyond Thu, 21 May 2009 18:32:38 +0000 hourly 1 http://wordpress.org/?v=3.0 By: david.yancey http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/comment-page-1/#comment-350 david.yancey Mon, 18 May 2009 13:58:46 +0000 http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/#comment-350 Another great example of where you can use this practice. Thanks for the comment. Another great example of where you can use this practice. Thanks for the comment.

]]> By: John Nolan http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/comment-page-1/#comment-346 John Nolan Sat, 16 May 2009 11:59:18 +0000 http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/#comment-346 Michael Feathers uses this method (in Working Effectively with Legacy Code) when attempting to understand a system before refactoring it to put it under test. I think he called it 'scratch programming'. He will hack into the code he is using applying tests to ascertain system behaviour and throw it away. I think it can be effective and I guess the use case I apply it too most often is fixing defects in complex code. I take the problem, isolate it, produce a proof of concept to reproduce and then I can apply different fixes to it without the worry of any other dependencies interfering. Michael Feathers uses this method (in Working Effectively with Legacy Code) when attempting to understand a system before refactoring it to put it under test. I think he called it ‘scratch programming’. He will hack into the code he is using applying tests to ascertain system behaviour and throw it away. I think it can be effective and I guess the use case I apply it too most often is fixing defects in complex code. I take the problem, isolate it, produce a proof of concept to reproduce and then I can apply different fixes to it without the worry of any other dependencies interfering.

]]>