Comments on: Attacking Technical Debt http://www.clarrus.com/2009/08/attacking-technical-debt/?utm_source=rss&utm_medium=rss&utm_campaign=attacking-technical-debt The Results are in the Team Mon, 16 Jan 2012 23:11:09 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jim Brosseau http://www.clarrus.com/2009/08/attacking-technical-debt/comment-page-1/#comment-19 Jim Brosseau Wed, 26 Aug 2009 21:00:59 +0000 http://www.clarrus.com/?p=1012#comment-19 ...the responsibility is on testing <em>and planning</em>. When we were building an ATC system iteratively, there were times when we replaced massive chunks of the underlying architecture. Each one of these was a project on its own, with the incorporation into the layers of the architecture planned out and validated at each stage before moving on, until it finally was 'just a part of the new mainstream'. For refactoring to work, there can't be any 'I hope things don't blow up when I push this button' moments... …the responsibility is on testing and planning. When we were building an ATC system iteratively, there were times when we replaced massive chunks of the underlying architecture. Each one of these was a project on its own, with the incorporation into the layers of the architecture planned out and validated at each stage before moving on, until it finally was ‘just a part of the new mainstream’.

For refactoring to work, there can’t be any ‘I hope things don’t blow up when I push this button’ moments…

]]> By: Geoff http://www.clarrus.com/2009/08/attacking-technical-debt/comment-page-1/#comment-18 Geoff Wed, 26 Aug 2009 16:26:16 +0000 http://www.clarrus.com/?p=1012#comment-18 Jim, when this refactoring works it is awesome but changing anything that is currently working is a very nervous proposition indeed. The responsibility being put on the testing activity is immense. All I can think of is that I would have loved to have been in the boardroom at Apple for the discussions on business ROI for all of this activity. Refactoring scares the crap out of me. Jim, when this refactoring works it is awesome but changing anything that is currently working is a very nervous proposition indeed. The responsibility being put on the testing activity is immense. All I can think of is that I would have loved to have been in the boardroom at Apple for the discussions on business ROI for all of this activity.

Refactoring scares the crap out of me.

]]>