New answers tagged

3

Reasons NOT to make big changes: One: The code is going away in a few months. Would it really be worth the company's time for you to spend 5 months fixing a system that will then be thrown away 1 month later? Caveat: Systems rarely go away when they are schedule to go away. The replacement system is almost always late, there are users who cannot upgrade for ...


0

Your problem is setting priorities: Which of the issues are showstoppers (in production)? Which are ticking timebombs? And which can be left in a while longer (because it works and has done so for years now, even sort-of)? What I would do in your situation is would make lists of problem classes that I would like to look at. E.g., replacing style="width=(\d+)...


1

I can of course do a global find and replace to get most of the issues out of the way, but that would mean my first commit would consist of thousands of changed .asp files. Can I do that? I don't see why not. A commit should be conceptually one thing, but I see no reason why a global find and replace from style="width=20" to style="width: 20px" would not ...


38

What you ask is not a technical question, and nobody here can answer it. You are working on a piece of software in maintenance mode, and you observe out-of-fashion technology and a large number of imperfections and inconsistencies. You ask what to do. Should you for example extend effort to make it cross browser compatible? Should you bring it in line with ...


14

When the application will be replaced in 18 to 24 weeks (adding the to be expected delays to the 6 to 8 week estimated presented above) then you really need to ask yourself what value you add to the business by still investing considerable amount of work in the old version. Sure, when you would be stuck with supporting the application for several years to ...


96

It sounds like you are confusing several things into the term "errors" legacy html attributes coding style coding errors which don't cause bugs unreported bugs mistakes which are now features reported bugs reported bugs you have been assigned to fix On a legacy app which is going to be replaced only one of these types of error should concern you. The ...



Top 50 recent answers are included