I recently tried to clean up some code by removing what appeared to be dead code after thoroughly searching for references and running tests. Unfortunately, it turns out it was part of a rare background process that didn't come up during our normal testing. After rolling back the changes and explaining the situation, I found myself feeling overly cautious about deleting anything again. How do other developers gain confidence that modifications or removals are genuinely safe?
5 Answers
In my experience with microservices, pinpointing unused code tends to be simpler since there are limited entry points. I usually ask around in our engineer chats first, then set up logging. If I don’t see any activity after a couple of months, I’ll remove the code responsibly. Also, having a tech debt README helps keep track of what might need to be pulled out.
Honestly, there's never a 100% guarantee that something is safe to remove. It's all part of the job, and there's even a term for it: "The Scream Test." If you find yourself wondering who uses a piece of code, just try turning it off and see if anyone screams!
Haha, the scream test sounds chaotic but accurate. I guess the best approach is to deprecate it first, monitor its usage, and then safely remove it after confirming nothing breaks.
I’ve made my share of accidents too, like deleting a production database table while I thought I was in development mode. Luckily, there was a backup available! After that, I learned to be more cautious and I still consider these experiences as essential to becoming a better programmer.
It's really key to communicate with your team and any stakeholders involved. Things can easily go awry, but it’s all part of the learning process. Congratulations on handling a real situation!
So the anxiety never really goes away, huh? Does experience help make it any safer?
After explaining what happened, make sure to write tests or at least put some guards in place to prevent a repeat incident. Every time I've skipped this step, I've ended up facing my past mistakes in the debugger later on.
Totally fair. I definitely plan to add more safeguards next time!
That seems like a solid approach. Asking peers first and monitoring activity is smart. Have you ever had any code hit the logs right before you were about to delete it?