Timeline for Effective way to estimate dead code removal?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2014 at 18:28 | answer | added | sixtyfootersdude | timeline score: 0 | |
| Dec 26, 2013 at 15:35 | review | Close votes | |||
| Dec 27, 2013 at 17:00 | |||||
| Dec 26, 2013 at 15:18 | comment | added | gnat | possible duplicate of I've inherited 200K lines of spaghetti code -- what now? | |
| Dec 24, 2013 at 6:16 | comment | added | Brendan | Create a copy of the project, rename all the old/dead stuff (e.g. append a "_old" prefix to names), then see how many "undefined class/method/whatever" errors you get when you try to compile. | |
| Dec 24, 2013 at 6:08 | comment | added | Doc Brown | Well, it would have been a good idea to mark every method beforehand when you were writing a replacement for it, to make it easy to remove it afterwards. Now it is a little late for that, but maybe not too late. Start adding comments with a searchable tag to all the dead functions. Then count the comments, this gives this will give you a rough feeling how much work you will have to invest. | |
| Dec 23, 2013 at 20:53 | comment | added | Aaronaught | I'd like to point out that static calls are a highly inappropriate way to add new code or architectures to a legacy operating environment. If you have any static coupling of new code to legacy code (or legacy data, for that matter) then you're not really improving matters at all. If it's a website, you should be able to just change a URL. And if it's a desktop, mobile, or other smart client, then it's not a good candidate in the first place for introducing a new technology stack without a complete rewrite - you need to make slow, incremental changes instead. | |
| Dec 23, 2013 at 19:38 | history | tweeted | twitter.com/#!/StackProgrammer/status/415204749722783744 | ||
| Dec 23, 2013 at 18:36 | vote | accept | ElderMael | ||
| Dec 23, 2013 at 17:57 | comment | added | Telastyn | Think: "It couldn't possibly take longer than ______ to get rid of that stuff!" Got it? What's the blank? Cool, now multiply by 3. The nuances of old codebases - particularly ones that grew organically are always troublesome and killing them always proves more difficult than anticipated. | |
| Dec 23, 2013 at 17:56 | answer | added | user53019 | timeline score: 6 | |
| Dec 23, 2013 at 17:52 | answer | added | jzd | timeline score: 3 | |
| Dec 23, 2013 at 17:44 | comment | added | Robert Harvey | Do you have a static code analysis tool that can identify the dead code? | |
| Dec 23, 2013 at 17:33 | history | asked | ElderMael | CC BY-SA 3.0 |