I am pretty weirded out by all the fellow software engineers I meet who just like, use git (the CLI program) directly. It seems crazy to me, like just writing

I am pretty weirded out by all the fellow software engineers I meet who just like, use git (the CLI program) directly. It seems crazy to me, like just writing every loop in assembly language because, you know, it's a loop, might be performance-sensitive. For day to day work, I use tools built on top of git, that present a much simpler workflow that is a tiny subset of what the CLI git program offers. Those tools include GitHub, Fork, SmartGit, our bug tracker's "New PR" feature, and e.g. my colleague's `pr-to-pr.sh` script, etc. I include among those "tools" the few CLI commands for things I do so often, it's not extra cognitive waste — simple things like "git pull", "git push", and maybe "git checkout -b hoge-hoge-branch". So it's not literally true that I don't use the git CLI command, but it is effectively true. To me, using git directly (aside from those few special cases) is like an "oh no, emergency!" type of action. Which does happen; I accidentally pushed commits to my local `main` branch or whatever, then I google it with kagi.com and like, carefully enter the right series of commands to rescue my work. But that shit would happen like, all the time if I just used git CLI as my main interface to git.