https://blog.mattwynne.net/2013/07/24/how-much-should-i-refactor/ Matt Wynne taking it one tea at a time Wed, 21 Aug 2019 12:53:52 +0000 hourly 1 https://wordpress.org/?v=6.2 https://blog.mattwynne.net/2013/07/24/how-much-should-i-refactor/comment-page-1/#comment-3106 Tue, 13 Aug 2013 20:34:23 +0000 http://blog.mattwynne.net/?p=529#comment-3106 I’ve been reading around and found some good discussions on design within agile by @scottwambler and @simonbrown

]]> https://blog.mattwynne.net/2013/07/24/how-much-should-i-refactor/comment-page-1/#comment-3045 Wed, 24 Jul 2013 19:49:28 +0000 http://blog.mattwynne.net/?p=529#comment-3045 Yeah 3:1 Matt!
Ummm dare i say it but does this raise an argument to do more thinking/design upfront?!
can you drill into a few of the refactors and see if they would or wouldn’t have been captured earlier?
It’d be a shame to think you’re in a product innovation team and 3/4 of your time is refactoring, no?

]]> https://blog.mattwynne.net/2013/07/24/how-much-should-i-refactor/comment-page-1/#comment-3044 Wed, 24 Jul 2013 15:55:46 +0000 http://blog.mattwynne.net/?p=529#comment-3044 Umm, 76:24 is closer to 3:1! Which feels about right.

]]> https://blog.mattwynne.net/2013/07/24/how-much-should-i-refactor/comment-page-1/#comment-3043 Wed, 24 Jul 2013 15:16:51 +0000 http://blog.mattwynne.net/?p=529#comment-3043 This is great insight, Matt!
It makes me think of this http://www.infoq.com/presentations/Technical-Debt-Process-Culture;jsessionid=EA22BC6DF3B87E9E7C75DC9773887074 which talks about the cost of not spending the time on refactoring.

]]>