I am convinced that the vast majority of professionals simply don't bother to remember and, ESPECIALLY WITH GIT, just look stuff up every single time the workflow deviates from their daily usage.

At this point perhaps a million person-years have been sacrificed to the semantically incoherent shit UX of git. I have loathed git from the beginning but there's effectively no other choice.

That said, the OP's commands are useful, I am copying them (because obviously I won't ever memorize them).

▲

freedomben 4 hours ago | parent | next [-]

> I am convinced that the vast majority of professionals simply don't bother to remember and, ESPECIALLY WITH GIT, just look stuff up every single time the workflow deviates from their daily usage.

I wrote a cheat sheet in my notes of common commands, until they stuck in my head and I haven't needed it now for a decade or more. I also lean heavily on aliases and "self-documenting" things in my .bashrc file. Curious how others handle it. A search every time I need to do something would be too much friction for me to stand.

▲

bluGill an hour ago | parent | next [-]

I refuse to have alises and other custom commands. Either it is useful for everyone and so I make a change to the upstream project (I have never done this), or it won't exist next time I change my system so there is no point. I do have some custom tools that I am working on that haven't been released yet, but the long term goal is either delete them or release them to more people who will use them so I know it will be there next time I use a different system.

▲

dheera 2 hours ago | parent | prev [-]

I just use Claude Code as a terminal for git these days. It writes up better commit messages than I would write anyway. No more "git commit -m fix"

	▲	freedomben an hour ago \| parent [-]
		indeed, I held off for a while but finally caved because I got sick of seeing commits with `git commit -m .` littered in there. These are personal projects so I'm the only one dev-ing on them, but still so nice to have commit messages.

▲

dec0dedab0de 32 minutes ago | parent | prev | next [-]

I just use my ide integrations for git. I absolutely love the way pycharm/jetbrains does it, and I'm starting to be ok with how vscode does. Remembering git commands besides the basics is just pointless. If I need to do something that the gui doesn't handle, I'll look it up and put it in a script.

▲

alwillis 2 hours ago | parent | prev | next [-]

> At this point perhaps a million person-years have been sacrificed to the semantically incoherent shit UX of git. I have loathed git from the beginning but there's effectively no other choice.

Yes! We mostly wouldn’t tolerate the complexity and the terrible UX of a tool we use everyday--but there's enough Stockholm Syndrome out there where most of us are willing to tolerate it.

▲

weedhopper 5 hours ago | parent | prev [-]

I’ve recently been looking into some tools that provide quick or painless help like pop up snippets with descriptions and cheat sheets, got any recommendations?

	▲	arcanemachiner 4 hours ago \| parent \| next [-]
		Navi is good for generating personal cheatsheets: https://github.com/denisidoro/navi But for Git, I can't recommend lazygit enough. It's an incredible piece of software: https://github.com/jesseduffield/lazygit
	▲	alwillis an hour ago \| parent \| prev \| next [-]
		Cheaters: https://brettterpstra.com/projects/cheaters
	▲	rusted_gear 5 hours ago \| parent \| prev [-]
		I've found tldr to be useful https://github.com/tldr-pages/tldr