Comments on: Technical debt, and the Death of Design: Part 2 http://kanemar.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/ Adventures in Agile Software Development and Scrum Thu, 19 Apr 2012 09:24:37 +0000 hourly 1 http://wordpress.com/ By: Kane Mar http://kanemar.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-9543 Fri, 10 Aug 2007 23:29:17 +0000 https://kanemar.wordpress.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-9543 To be honest, I haven’t even tried to fully explore how to address technical debt. This is because there is already an excellent book about the topic: “Working with Legacy code”, by Michael Feathers.

If you haven’t ready read this book then I’d strongly encourage you to run (don’t walk!) to your nearest bookshop and order it.

]]> By: Sergiu Rata http://kanemar.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-9535 Fri, 10 Aug 2007 04:07:21 +0000 https://kanemar.wordpress.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-9535 It looks like you’re describing only two approaches: continue working on existing system or working a brand new one. How about the refactoring approach? According to Joel Spolsky this is one the thing that software should not do: http://www.joelonsoftware.com/articles/fog0000000069.html

]]> By: pligg.poddrzewem.pl http://kanemar.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-6734 Sat, 03 Mar 2007 20:32:42 +0000 https://kanemar.wordpress.com/2006/08/07/technical-debt-and-the-death-of-design-part-2/#comment-6734 Technical debt, and the Death of Design: Part 2

Part two of Kane Mar’s brilliant article describing technical debt. The term is used to describe long term consequences of decisions that lead to meeting the deadline met but compromising the quality. Quoting Ken Schwaber: “You don’t need to buy cra…

]]>