this post was submitted on 03 Mar 2024
1100 points (97.7% liked)

Programmer Humor

20703 readers
632 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
 
(page 3) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 38 points 11 months ago (17 children)

So do you guys pronounce it git or jit

load more comments (17 replies)
[–] [email protected] 33 points 11 months ago (5 children)
load more comments (5 replies)
[–] [email protected] 71 points 11 months ago (3 children)

I once had HR ask if I was familiar with G-I-T ( she spelled it out), for a moment, my only thought was "wtf is G-I-T".

[–] [email protected] 18 points 11 months ago (3 children)

One of my first interviews in Canada I was asked what a “zed-index” is and was like what? A what now?

load more comments (3 replies)
load more comments (2 replies)
[–] [email protected] 17 points 11 months ago (1 children)

As someone who knows that they know very little about git, this thread makes me think I'm not alone.

[–] [email protected] 19 points 11 months ago (1 children)

I think advanced git knowledge, like RegEx, is the exception, while the norm is to know the tiny handful of day to day useful bits

[–] [email protected] 10 points 11 months ago (2 children)

How is regex git knowledge? I guess you can use regular expressions with git grep but it's certainly not a git-oriented concept...

[–] [email protected] -1 points 11 months ago (5 children)

I don't even know how to respond to this considering it has nothing to do with what I said...

load more comments (5 replies)
[–] [email protected] 17 points 11 months ago (1 children)

what. that's not what they said. they are comparing git knowledge to regex knowledge.

[–] [email protected] 10 points 11 months ago (1 children)

Ah, thanks for the explanation. I too misunderstood the inflection.

load more comments (1 replies)
[–] [email protected] 7 points 11 months ago (1 children)
[–] [email protected] 5 points 11 months ago (1 children)
cat ~/.bash_history | grep "gut add" | wc -l

I've typed that more times than I thought...

[–] [email protected] 5 points 11 months ago (1 children)
[–] [email protected] 2 points 11 months ago

echo alias gut=git >> ~/.bashrc

[–] [email protected] 6 points 11 months ago (1 children)
[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

You don't just git to edit past commit

[–] [email protected] 20 points 11 months ago (1 children)

git blame is another good one

[–] [email protected] 8 points 11 months ago

Yes, I think we all like to blame git

[–] [email protected] 2 points 11 months ago
[–] [email protected] 12 points 11 months ago (1 children)

Learn to use git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.

[–] [email protected] 10 points 11 months ago

With automated CI, I've had very few times where bisect is useful. Either the bug was introduced 1-2 commits ago, or it's always been there and the exact commit is irrelevant to the solution, since you just fix it forward.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

How about git commit-tree [Hash] -p branch1 -p branch2 … -m "Dummy Message"

load more comments
view more: ‹ prev next ›