Never delete code immediately. Always comment it out first.

Or use source control.

Like I always do :)

@filthyranter I sometimes commit commented code if its code to be, where the dependencies are not in place.

Writing a stub, commenting it out and adding a todo line so it shows up in the todo list is a good way to quickly finish up once all else is done.

@Olverine @filthyranter Of course. I should've made it clear.

I was carefully doing the Ctrl-Z Ctrl-Y surgery to get back the code I deleted prematurely. The dev saw me doing this a couple of times and decided to drop those words of wisdom that would guide me to this day.

Soft delete - staying in legacy until the end of times :D

Why oh why?

Use local history of your IDE. Use version control. Never let commented code stick around.

I consider this an anti-pattern.

This is exactly why our codebase is littered with commented out code.

My colleagues adhere to your advice, but then always forget to delete it before committing...

On the plus side, technically, our codebase has lots of comments 😜

You fucked up rollback this file to orogin Head on git :P

Never delete C code. comment it out, but prefix it with a newline trigraph so that it looks like a comment but still executes.

No worries when using Android Studio since it has local history. Xcode sucks it doesn't have that feat 😑

I learned that the hard way in my very initial days of programming.

When I'm about to rewrite some code, I always comment out the old code first, sometime i can reuse some of the old code.

Make sure you don't commit commented out code, one of our projects is full of commented out code and nobody dares to remove them (because they *might* be "important")

Words to live by.

@filthyranter and thats where source controll like git is the way to go.

Especially since commented code might not light up as removed in a diff, at least not at clear.

So every “rule” has its exception :)