813

submitted 1 day ago by ipconf@lemmy.ml to c/programmer_humor@programming.dev

118 comments fedilink hide all child comments

Yeah learned this the hard way.

you are viewing a single comment's thread
view the rest of the comments

[-] cmhe@lemmy.world 17 points 1 day ago* (last edited 22 hours ago)

Isn't it the exact opposite?

I learned that you can never make a mistake if you aren't using git, or any other way for having access to old versions.

With git it is really easy to get back to an old version, or bisect commits to figure out what exact change was the mistake.

The only way I understand this joke is more about not wanting to be caught making a mistake, because that is pretty easy. In other methods figuring out who did the mistake might be impossible.

[-] fibojoly@sh.itjust.works 4 points 1 day ago

You're confusing errors in your code, and errors while doing some git command you thought you knew. Lucky you, it's clearly never happened to you because you don't mess around with it.

[-] cmhe@lemmy.world 1 points 22 hours ago* (last edited 22 hours ago)

Sure, I sometimes messed up with git, but a git reset , checkout, rebase or filter-branch (In the extreme cases) normally fixes it, but real issues are very rare. And I use git a lot... But only the CLI, maybe people have issues with GUIs?

[-] AeonFelis@lemmy.world 5 points 21 hours ago

[-] ezterry@lemmy.zip 1 points 20 hours ago

Funny those are commands I avoid.. They all have to do with editing history which I know there is a vocal group here that loves "clean" history but that isn't what happened.

sure merge full features so you can roll back a feature.. And if something is really off I might start from a snapshot commit and cherry pick/merge a bunch in but usually history is histoy.. If submitting to a public project I may make a new branch with the cleaned version but why edit in line. That is risking issues.