Programming

17484 readers

72 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

559

Julia Evans' Git cheat sheet (programming.dev)

submitted 1 month ago by [email protected] to c/[email protected]

57 comments fedilink hide all child comments

Git cheat sheets are a dime-a-dozen but I think this one is awfully concise for its scope.

Visually covers branching (WITH the commands -- rebasing the current branch can be confusing for the unfamiliar)
Covers reflog
Literally almost identical to how I use git (most sheets are either Too Much or Too Little)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -2 points 1 month ago* (last edited 1 month ago) (1 children)

GUI users = low skill ✅

Majority GUI a weak subset and of little use ✅

Elitism ✅

Of course, this is all couched in “use what you like”, and top it off with a general sentiment of how this post is all but useless.

If someone has to ask you for your git fu help the problem isn’t GUI use it’s the incompetence and/or inability to solve it yourself. Implying a strong correlation of the two is where I take issue.

My personal experience? A built in GUI saves you so much time like the one in JetBrains IntelliJ, if I need something more use case oriented that is more than the core fn (intelliJ’s does not simply include fetch/push/pull, but much more including everything in the graphic) then I click terminal tab and do what I need. Similarly the git tree provides an immediate view and context of the branches, changes, tags etc.

It’s almost like filtering people into GUI and CLI boxes doesn’t really work.

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

I think you're making a lot of misinterpretation; but that's up to you...

But, just so that I can understand correctly... When you're saying: "if I need something more [...] I click terminal tab"

That "terminal tab" of yours, it's a CLI isn't it?

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

It probably is, but I think their main point is the protest against the age-old delineation into "GUI vs CLI" camps. I'm not saying that you're elitist, even if your statement might be interpreted as such (it's hard to communicate tone online but the quotations around "their workflow" could appear mocking), but regarding the structure of your statement, I had a "Windows users are all button-presser noobs" phase and would've typed something similar about the Git CLI if time was decently rewound (sans the kindness of a "use what you like" statement). They could be interpreting your statement as a propagation of the anti-GUI stereotyping.

Evidently they prefer GUI but can effectively use the CLI -- no one disagrees that the CLI is more functional.