A good method to handle a large number of unused or obsolete functions in code

We are currently facing the following problem in our application:

About 40% of the code in the application is never used. This means that the code will be there and possibly functional, but the Frontend function was disabled so that users could no longer achieve functionality or other methods replaced the old, now obsolete methods .

What I'm doing now is deleting all the old code when you are not trying to break anything, manually.

Question:

  • You will delete the old code or hope that it may wake up for a while ... zombie - like
  • Do you find it worth the effort to remove the code (less work to find things in a mess, better testing coverage, easier for other people to find their way).
  • Should we store the code somewhere, like a link? (We use Version Control, but I find it quite difficult to find the old code in the Jungle edition ... any tips for this?)
  • Do you have any arguments for convincing the team / management / developers who wrote the code?
  • Reasons not to discount and then remove code?

TL DR: delete unused code or leave it as is? Discuss!

and

+3
source share
2 answers

, , . , , , - , .

, , , ( , , , , , ...)

, API, , , , /, , , ( ).

+4
  • , ... zombie - like

. , .

  • , ( , , ).

, , .

  • -, ?

, , ?

+2

Source: https://habr.com/ru/post/1780880/


All Articles