Best Practices for Removing Unused Code

Question

I\'d like to know what people\'s best practices are for removing unused code. Personally I\'m a fan of deleting (not just commenting) anything that\'s not currently being used.

Answer 1

My guess is that even if you comment that it's in the repository, it'll be re-written instead of someone going back and grabbing it.

Not that I've worked in many places with this "no code left behind" policy (just one), but I've NEVER seen someone go back into the repository and get some old code.

However, except for small blocks, I've never seen anyone uncomment someone else's code either!

If you wanted to save it, I'd leave it fully implemented and tested (check in the tests!) but under a condition that will change if the new code is ever needed.

I've had un-needed code just "Turn on" when it was needed, that's a really nice feeling (not that it can always be done).

If you can't be bothered to make it fully functional and tested, then snip it and let the next guy re-write it.