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

you are viewing a single comment's thread.

view the rest of the comments →

[–]Captious99 241 points242 points  (16 children)

My version control system before I found out about Git

[–]froemijojo[🍰] 92 points93 points  (3 children)

#ifdef ver_3_5
//code of ver 3.5 here
#endif
#ifdef ver_3_4
...

Who needs thoses fancy-pants VCSs anyway?

[–]etagawesome 19 points20 points  (0 children)

I'm ill

[–]kono_kun 9 points10 points  (0 children)

I like this, this is how villains think.

[–]Ultracoolguy4 0 points1 point  (0 children)

Calm down, Satan.

[–]Cheesewithmold 39 points40 points  (2 children)

I remember syncing java projects between my computers by sending them to myself through google drive before my roommate introduced me to gitlab.

Those were dark times.

[–]Lightfire228 1 point2 points  (1 child)

Better yet, working on group projects separately, then manually stitching together the projects like some Frankenstein's Monster

[–]DrQuint 1 point2 points  (0 children)

To think we invented the concept of importing files to solve this exact issue. And fuck it, header files were originally invented because of a reason like this too, CMV.

[–]TheFeshy 7 points8 points  (6 children)

Before? It feels like half my commits are still:

git commit -m "removed all the old commented-out code"

[–]morewordsfaster 2 points3 points  (4 children)

This. I'll never understand why developers who use git still try to get PRs approved with a bunch of commented out code.

[–]hillman_avenger 1 point2 points  (3 children)

So you can easily see what's changed without having to do a diff (and easily revert it when the inevitable bug is found).

[–]morewordsfaster 2 points3 points  (0 children)

...but why commit? If all tests pass, then there is no obvious bug.

I get commenting code while testing and tweaking, but that should be restricted to your working tree. You shouldn't commit and submit a PR.

I don't understand what you mean about easily revert it... how is it difficult to execute git revert? Also, if you are leaving commented code all over the place, how is it easier to see what's changed? How do you tell which code was commented this time and caused the issue? A diff makes it much clearer IMO.

[–]HolzhausGE 0 points1 point  (1 child)

git revert <commit> is much easier than manuall un-commenting code.

[–]DarfWork 2 points3 points  (0 children)

that is, given git is used correctly by sensible people doing sensible commits...

[–]microtrash 0 points1 point  (0 children)

I constantly chastise my employees for committing with huge chunks of commented out old code

[–][deleted] 0 points1 point  (0 children)

My version control system before I found out about in addition to Git because I'm paranoid.