- cross-posted to:
- git@programming.dev
- cross-posted to:
- git@programming.dev
Title text: If that doesn’t fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of ‘It’s really pretty simple, just think of branches as…’ and eventually you’ll learn the commands that will fix everything.
Transcript
[Cueball points to a computer on a desk while Ponytail and Hairy are standing further away behind an office chair.]
Cueball: This is git. It tracks collaborative work on projects through a beautiful distributed graph theory tree model.
Ponytail: Cool. How do we use it?
Cueball: No idea. Just memorize these shell commands and type them to sync up. If you get errors, save your work elsewhere, delete the project, and download a fresh copy.
This is helpful when you get errors: https://ohshitgit.com/
Git --gud
A good GUI can solve most problems.
If my colleagues mess something up in their fancy GUIs, they come to me to fix it in the terminal.
I’m using Mercurial for the last 2 years at current company, before that it was 5-7 years of Git on various jobs. It’s so much better if you use it correctly (no long-living or big branches). I forgot what hell Git was sometimes.
I used hg until python switched to git.
if python isn’t going to bother them the battle is lost.