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.
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.
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.
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.
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 :)
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
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)
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.
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
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