this post was submitted on 20 Nov 2024
869 points (97.5% liked)

Programmer Humor

19843 readers
6 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 2 years ago
MODERATORS
869
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 30 points 1 month ago (2 children)

The problem is that these are “source control basics” that everyone needs to learn the hard way once it seems.

Waiting 3 months in between commits however is a really bad rookie mistake because you were worried about making a commit that wasn’t perfect.

[–] [email protected] 8 points 1 month ago (1 children)

the problem is that VS Code ran git clean if you clicked yes, which is completely idiotic behavior. No other git client, text editor, or IDE on the planet does that.

[–] [email protected] 1 points 1 month ago (1 children)

Either way, waiting 3 months worth of work before a commit is the big mistake here.

[–] [email protected] 5 points 1 month ago (1 children)

I think they hadn't ever used git before, and according to at least one person in the linked issue, vs code might have auto initialized the git repository for the user.

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

In fairness, ALL git terms feel backwards at first.

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

Imperfect commits never existed when you squash.

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

Squash ftw. Simpler clearer history.

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

Interesting. I wouldn't know, because I code everything perfectly the first time.

Disclaimer: The above flagrant lie was brought to you by my also using rebase and squash to hide all of my mistakes.