It's never actually useless code, it's the code that is _almost_ there. Then there's the whole political dance where one team still uses it because the replacem

It's never actually useless code, it's the code that is _almost_ there. Then there's the whole political dance where one team still uses it because the replacement isn't quite the same and now you're solving some obscure use case and prioritizing the work gets done. Plus, it's likely the original author is still present so you have to placate them too. I definitely take on the grim reaper role and make deletions happen. But it does take all the skills in the post.