Understanding Git concepts is easy. That takes like an hour. Understanding what it does when you type the command is hard. That part only comes from memory and the fear of explosions when you type the wrong thing.
Also bad architectural problems can be magnified with git. I used to work at a place that migrated an insane number of custom files into a single git-repo, and basically git add -A would result in silently adding thousands of files to your push, because it was configured to hide changes since it was so big you couldn't actually see the files you changed. Which meant manually tracking your file names on notepad and only adding those.
“A computer lets you make more mistakes faster than any other invention with the possible exceptions of handguns and Tequila.”
― Mitch Ratcliffe
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Understanding Git concepts is easy. That takes like an hour. Understanding what it does when you type the command is hard. That part only comes from memory and the fear of explosions when you type the wrong thing.
Also bad architectural problems can be magnified with git. I used to work at a place that migrated an insane number of custom files into a single git-repo, and basically git add -A would result in silently adding thousands of files to your push, because it was configured to hide changes since it was so big you couldn't actually see the files you changed. Which meant manually tracking your file names on notepad and only adding those.
“A computer lets you make more mistakes faster than any other invention with the possible exceptions of handguns and Tequila.”
― Mitch Ratcliffe