Deleting code is so therapeutic. Right?

So is production database.

Deleting code can be when you have

- function1
- function1-new
- function1-new_new
- function1_v2
- function1_no_use_this
- function1_v3
- function1_v3_dont_use_others
- function1_master

All in use and all do different things to each other and return different data, im too fucking scared to delete them.

@thevariableman, I don't mind that, multi db collisions (master/slave scenarios) take you for a pleasure ride.

Deleting code is scary.
Deleting files is great.
Deleting projects is so much better.

And better still?
$ sudo shred -zfu -n 64 ~/company/from/hell/projects

I can't think of many things more satisfying than that.

@Root download repo and delete every day win-win

Oohh yes. I'm tidying up a lot of unused old code at the moment as part of a separate migration project. Feels rather good.

Deleting code is by far the most horrific thing. You always need that part you deleted again.

Yes, it gives me fewer things to worry about.

Not particularly deleting though. I would call it trimming the dead parts.

And if you suffer from hitting ctrl-z everytime, use fucking git.

Git rid of the dead parts.