this post was submitted on 20 Nov 2024
442 points (97.4% liked)

Programmer Humor

19623 readers
1253 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
442
submitted 9 hours ago* (last edited 9 hours ago) by [email protected] to c/[email protected]
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 17 points 41 minutes ago

let's turn this into a constructive angle for future devs and current juniors: just learn git cli, I promise you it is much simpler than it seems.

all those memes about git having like a thousand commands are true, but you really will only use like 7 at most per month.

learn push, pull, merge, squash, stash, reset, im probably missing like one or two

I promise you again: it is much simpler than it seems. and you won't have to use these stupid git GUI things, and it will save you a hassle because you will know what commands you are running and what they do

short disclaimer: using git GUI is totally fine but low-key you are missing out on so much

[–] [email protected] 6 points 21 minutes ago

I fucking HATE when abstractions over git use cutesy names that git doesn't use.

[–] [email protected] 22 points 2 hours ago

Poor guy basically did a git reset —hard HEAD without even a git repository

[–] [email protected] 51 points 2 hours ago (2 children)

I feel bad for this kid. That really is a bad warning dialog. Nowhere does it say it's going to delete files. Anyone who thinks that's good design needs a break.

Half the replies are basically "This should be obvious if your past five years of life experience is similar to mine, and if it isn't then get fucked." Just adding insult to injury.

[–] [email protected] 14 points 1 hour ago (1 children)

I'm not great at English, but "discard all changes" shouldn't ever mean "Delete".

[–] [email protected] 5 points 57 minutes ago

In the context of version control it does. Discarding a change that creates a file means deleting the file.

[–] [email protected] 21 points 2 hours ago (2 children)

Also, why not send them to the recycle bin? I never really thought about it before, but that does seem a reasonable UX improvement for this case

[–] [email protected] 1 points 21 minutes ago

I wonder if there's already a git extension to automatically stash the working tree on every clean/reset/checkout operation...

[–] [email protected] 1 points 43 minutes ago

Because “the underlying Git nukes them right away, so why shouldn’t we perma-delete the files, too?”

Anything else’d be effort…

[–] [email protected] 7 points 1 hour ago

Jesus saves, and so should you

[–] [email protected] 9 points 2 hours ago (2 children)

If you ever happen to have 5000 uncommitted files, you shouldn't be asking yourself if you should commit more often. You should be asking yourself how many new repos you should be making.

[–] [email protected] 25 points 2 hours ago (1 children)

The person didn’t have any git repository; probably a new programmer that didn’t know how version control works and just clicked discard without understanding what that means in this situation.

[–] [email protected] 2 points 33 minutes ago

This person is why we have that meme where devs would rather struggle for a week than spend a few hours reading the documentation.

[–] [email protected] 3 points 1 hour ago

This is without gitignore, so probably just installed one js dependency

[–] [email protected] 0 points 23 minutes ago (1 children)

Honestly no idea why someone would go around a completely unknown menu in a new unknown editor and randomly click things with caution completely out the window. Not having a copy or trying a blank project, not even reading any messages. I mean even if we don't know it's a nuke button, God knows what other edits it could do to your code without you knowing.

This goes beyond rookie mistake. This is something 12 year old me would do. Same with the issue page being 90% swear words.

[–] [email protected] 2 points 15 minutes ago

Honestly no idea why editors give shit random names instead of using the terms git uses.

[–] [email protected] 27 points 4 hours ago (5 children)

Looks like someone forgot about the 3-2-1 rule. Teachable moment.

load more comments (5 replies)
[–] [email protected] 2 points 2 hours ago

Maybe he would prefer perforce.

[–] [email protected] 20 points 5 hours ago (2 children)

deleted a chunk of my work the other day by pressing Ctrl z in windows explorer. my project was without source control installed (cuz it was in Dev stage), and Ctrl shit z/Ctrl y hotkeys didn't work, so that chunk was just gone, persished forever... or so I though. I remembered vs code having a file history under some panel. found it, and here it was - at least some of the latest history of my file. lesson learned: even in Dev where nothing is yet working, finish your day of coding with a commit to a remote repo.

[–] [email protected] 11 points 3 hours ago (2 children)

all I'm learning from these stories is to stay far far away from vscode.

[–] [email protected] 2 points 1 hour ago

You can avoid this problem by not doing version control in your code editor. Different programs for different purposes. VS Code is fine for editing code and should not be used to manage an entire project.

[–] [email protected] 2 points 2 hours ago

I begrudgingly switched to vscode a few years ago. I've never had any issues like this with it. My only issues have been with a plugin that I installed optionally (and that was later fixed by the plugin author).

load more comments (1 replies)
load more comments
view more: next ›