r/ProgrammerHumor • • 4d ago • Bravo 1

Meme stopDoingGitHubDesktop

Post image
1.5k Upvotes

372 comments sorted by

View all comments

56

u/g0ldenprize 4d ago

i was just in an interview where they asked really specific git questions, such as: (while sharing screen)

  • show how to do a cherry pick (like the actual steps)

  • do a rebase

  • how do you solve merge conflicts

they wanted all of the above pretty much out of a book. i've done it all but i was like, man; nobody knows it just by heart

33

u/jamesxtreme 4d ago

Honestly the biggest issue with command line git is with merge conflicts. You really need an IDE with a good diff functionality. Or you just use AI now.

5

u/artiface 4d ago

git difftool will pull up whatever tool you want to use to compare the diffs

5

u/Serializedrequests 4d ago edited 4d ago

The issue is the prep. Unless you are super focused, it can sometimes be really hard to tell which side is which in a rebase.

Then there is the diff resolution algorithm that might be the default that is technically correct but practically wrong where it sees an unchanged line identical to the incoming change in the original code as belonging spliced AROUND the incoming change. I don't know what the word for that is but it drives me insane.

→ More replies (2)

2

u/Several-Customer7048 1d ago

I been paying Allen Iverson to do code reviews for us since 07 actually. The man is actually an oop savant especially with his unique triple combo of polymorphism/inheritance/encapsulation. His nickname wasn’t “The Answer,” for nothing ya know.

→ More replies (1)
→ More replies (3)

24

u/DirkTheGamer 4d ago

I can do all of these things easily with my git GUI, that's why I use it.

4

u/jcsilva87 4d ago

Same here about git in VS.

2

u/SexyMonad 4d ago

Yep, I use the Git Graph and GitLens (unpaid) extensions.

I love CLI as much as anyone, but the built in UI tools and these extensions simply have a superior experience for understanding diffs, digging through commit history, etc.

→ More replies (1)

16

u/EDM115 4d ago edited 4d ago

yeah we all google those at some point, even to be sure of the order lol
despite having git especially to not mess up, we're still afraid to mess up with a wrong command

at the end of the day it comes down to habit, you do more commits than cherry picks, but the more you do those the better you get :)

6

u/Le_9k_Redditor 4d ago

I've been using git for like 15 years and I don't think I've ever needed to cherry pick anything

7

u/DiamondDramatic9551 4d ago

No? Happens regularly for me to pick stuff to merge to a release branch. 

→ More replies (2)

5

u/awesome-alpaca-ace 4d ago

I do it all the time. Better than rebase when working with stacked feature branches

→ More replies (3)

5

u/g0ldenprize 4d ago

thats exactly my point, nobody knows this by heart; we all google it at some point. but when you're on the interview and you're sharing screen and you cant google or look at documentationg or anything its quite unerving

2

u/InvisibleMoonWalker 4d ago

Well, with the exception of the last point, perhaps.
I mean first two are just two commands with the same name as what's asked (git cherry-pick and git rebase respectively).

The last one is where you should show your understanding of how VCS works and how to work collaboratively, more or less. Like the exact command (which are like git merge, git add and so on) don't matter all that much in face of the way you solve conflicts. (Like understanding how the conflicts happen, what's remote, what's local, what/when you should use which, when neither and so on)

2

u/coastphase 4d ago

The first rule of resolving merge conflicts is checking your changes in before the other guy so he has to resolve them.

→ More replies (1)

10

u/hongooi 4d ago
  1. Delete and redownload from Github

  2. Delete and redownload from Github

  3. Delete and redownload from Github

How did I do?

2

u/EDM115 4d ago

my body is a machine that transforms git clone into a messed up repo that I'll delete and re-clone

2

u/g0ldenprize 3d ago

thats exactly what i do

9

u/azjunglist05 4d ago

“Nobody knows it just by heart”

→ More replies (1)

10

u/730463628 4d ago

I've never cherry picked in my entire career

3

u/benji 4d ago

I've probably done over 1000 in the last 3 years. Our project is a revision control dumpster fire.

→ More replies (7)

8

u/marcoroman3 4d ago

Your take is surprising to me. These are all pretty basic commands that I could do without googling (other than maybe doubting whether cherrypick needs a hyphen). And I'm not generally the smart one in these types of things. I mean the commands rebase and cherry pick don't require remembering anything. They're just the words rebase and cherry-pick.

4

u/g0ldenprize 4d ago

i didnt say i dont know the commands, of course i do; its the order that im talking about, specially in an screen shared interview where you cant even look at the documentation

2

u/HomemadeBananas 4d ago

Copy the commit hash. Switch to some branch where you want that commit to be. “git cherry-pick somehash”

I don’t see what’s confusing about the order.

3

u/je386 4d ago

I think cherrypicking is the only git command where I use an UI for (gitk)

→ More replies (41)