Re:Code sucks
by bmohlenhoff on Saturday December 01, 2012 @10:53AM
(#4857942)
I agree. The temptation to roll over existing changes when inheriting a new codebase can be overwhelming at times, and the only sensible way that I've found to deal with it is to consider the impact to the schedule and how that ties into the overarching business need for whatever it is that you're working on. Without a bit of discipline here, I've found that it's way too easy to start working on things that don't advance the project towards its overall goals.
Re:Code sucks
by LeonidBugaev on Saturday December 01, 2012 @10:52AM
(#4857938)
Good point.
It's never perfect.
So what I do is for every chunk of code I think needs to be replaced or solidified I ask myself first how it will impact my schedule, how it will impact other coders as they do maintenance, if the end goal is a better user experience, and if so does that serve the business? From answering these questions I can determine if we should make a change now, or if we want we can defer the change to a specific place in our timeline and plan it out. This has worked well for me in the past.