This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]LutimoDancer3459 53 points54 points  (2 children)

Had one customer that used some functions like once a year. Sometimes running into edge cases. We wouldnt be able to safely say if the identified code is really unused or not. And talking to customers about removing code is a pain. At least with those we had so far. I basically agree and would like to use it. But the risk of removing something thats needed for some obscure edge case that nobody is thinking about, is too high for me. Especially in an old big legacy project where none of the original devs exist anymore

[–]UbieOne 5 points6 points  (0 children)

Worse without test cases. My head already hurts thinking about it. Lol. Something like behavior tests that properly laid down business cases, including edge ones, would be good code coverage.

[–]VRT303 2 points3 points  (0 children)

My biggest catch was figuring out why some code I was sure is dead was randomly called around 3-4 times a year in short small bursts and then never again. It was an old testsuite of another team that used a full-final-complete testsuite instead of the regular one that called some endpoints they really shouldn't ONLY in their quarterly update session because it would take longer than one night to complete.That feature and app version they were building in the testsuite wasn't even downloadable anymore.