tag:blogger.com,1999:blog-5724099066106449846.post1738293660098875410..comments2023-12-31T02:09:31.149-05:00Comments on Madking's Musings: Code Maintenance - You Can't Afford to Not Do ItMichael Haddox-Schatzhttp://www.blogger.com/profile/02782657000665338948noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5724099066106449846.post-25191813651577019862011-01-04T12:52:26.502-05:002011-01-04T12:52:26.502-05:00Good post. Though sometimes it can be tricky to co...Good post. Though sometimes it can be tricky to convince others that it is better to take the time *now* to implement the new feature in the cleanest way possible, especially if everyone is under pressure and the 'hack solution' can be implemented more quickly. After doing this for 10.5+ years, I just assume that refactoring and trying to implement things cleanly the first time is part of my time estimate for getting things done. When I started at my current job 6.5 years ago, I would initially ask my boss for time to refactor; now I realize it is best to just do it.<br /><br><br />One quibble: I don't know that I agree that 'most code starts out fit'. Sometimes, when requirements are initially unclear, the best thing to do is hack something up quickly that will be quite 'unfit'. Once you have code that does *something*, requirements can suddenly become clearer, and then the original code can be refactored/rewritten.J. M. Haddox-Schatzhttps://www.blogger.com/profile/00780728498109025504noreply@blogger.com