- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
- Back when I was still on Reddit, I made a comment on a chess sub saying that in chess you are not allowed to make your king “commit suicide” to explain how a stalemate works. One day later I got a message about suicide prevention because someone flagged me for promoting suicide. - What a dumb site. - I mean in all fairness it was probably a bot that flagged that. - By the time I left (API shenengigans) Reddit was already a place where bots interacted with bots half the time. - One of my favorite moments on reddit was spotting a bot that spouted unrelated nonsense. I checked the comment history and found users responding earnestly to the nonsense. While it was hilarious, it was also quite sad, the state of those people. - One of the funnier ones for me was a “your words are in alphabetical order” bot replying it to the haiku-bot that replied to the human first. The alphabetical-order bot didn’t reply to te the human as well; but to the haiku-bot, mind you! 
- What people? “It’s bots all the way down, of course!” 
 
 
- They should have known you were just horsing around. - He got pawnd! - Google helpline numbers 
 
 
 
- It’s too late for me. My coworker pull requested before I could and now I think I’m going to commit merge conflict. - Just base your stuff on their stuff and hassle everyone to merge that other PR. 
 
- That’s not a mistake git can do that to people. Especially those who have never used git via command line. - Yeah, imagine you accidently commit over weeks of work, or hell, if it’s the main branch, and you deleted the other origin branch prior to merging, it could be a lot more than a few weeks worth of work. The revert to a previous commit… shutters. - I don’t know if you’re joking, but in case you’re not: - git reflogand- git reset --hard HEAD@{n}is your friend. You can undo almost anything. Deleted commits and branches aren’t really deleted. Remotely deleted branches can be pushed again.- Except for an (accidental) - git restore/- git reset. Those are permanent and can’t be undone.- Even - git resetcan be undone by a lot of editors. At least IntelliJ has an excellent local history that works much like git. Sure it’s a pain if you touched several files but that’ll teach you to atomify your commits.- Edit: Plus, - git resetitself does nothing of note really, but I’m sure you know. Needs the- —hardflag to do any meaningful damage.
- Except for an (accidental) - git restore/- git reset. Those are permanent and can’t be undone.- Unless, you didn’t close your editor before doing so, in which case, you can just save it again. - I’m not talking about IDEs. 
 Even Kate gives you the option to either discard the deleted document/changes or keep them and save again.
 
- Its even scarier when master branch is prod - Don’t tell me ghost stories right now, it’s almost my bedtime. 
 
- That’s when you call in a wizard. - They do git necromancy and sacrifice a goat to the reflog to recover your code - Ah, yes, the reflog incantation. It is said that it can be performed only by those who have rebased on an hard reset origin. 
 
 
 
- That’s a really long phone number. Crazy that it has 7 repeating numbers in succession. - Considering suicide? Type in these 18 numbers without mistakes while you think about it… - 0118 999 88199 9119 725 3 - That’s easy to remember! 
 
 
 
- @@ -1 +0,0 @@ - -my existence 







