tag:blogger.com,1999:blog-4900151497087138627.post6345943485416816517..comments2022-04-07T07:57:47.881+02:00Comments on Information is king: When is refactoring unappropriate?Rune Sundlinghttp://www.blogger.com/profile/10334374587401199926noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4900151497087138627.post-75717875552869516332008-08-30T20:10:00.000+02:002008-08-30T20:10:00.000+02:00Try adding maintaining two branches in that scenar...Try adding maintaining two branches in that scenario and let's say the code is following the "magic push button" paradigm. Ohh.. Nice. <BR/><BR/><BR/>My suggestion is that one should consider doing dedicated Sprints/Iterations where the entire team does nothing but refactor to avoid these kind of scenarios. This would ofcourse be something the Product Owner should recognize as a way to go. Something they seldom do.<BR/><BR/>Great post and a great point. Been there for 6.5 years, so I know a great deal about this subject. :)Anonymousnoreply@blogger.com