News for hackers. Stuff that matters.
Re:How to Improve a Legacy Codebase by jacquesm on Tuesday May 30, 2017 @07:10PM (#14449316)
Yes, but those are special cases. For every rule there is an exception, and of course if the parts above apply you are fully in control and are well able to judge whether you should rewrite or not.

But the situation that I'm describing is not ticking any of those boxes and I think I made that quite clear in the pre-amble.

Re:How to Improve a Legacy Codebase by rattray on Tuesday May 30, 2017 @07:26PM (#14449395)
> the situation that I'm describing is not ticking any of those boxes

Oh, there's no doubt in my mind about that!

Some people may read this and extrapolate too far regarding their own situation (there's a reason this is a specialty field, it's hard stuff).

Re:How to Improve a Legacy Codebase by jacquesm on Tuesday May 30, 2017 @08:41PM (#14449731)
One thing that bothers me is that people tend to expect miracles. I usually tell them it will take as long as it took to fuck it up to fix it. But that doesn't mean that you can't have some initial results to point the way in a short time. It's more about establishing a process and showing that there is a way out of the swamp than that it is something super tricky or difficult. Just follow the recipe, don't let yourself be distracted (this can be really hard, some management just can't seem to get out of the way) and keep moving.