|
|
|
|
|
|
by iliaznk
2183 days ago
|
|
|
Git is not complicated. Version control is. If you sit and think hard enough about what you'd want a VCS to do, you'll come up with about the same set of features, I believe. And then think about how you'd implement those in an abstract CLI tool. So, as I said, it's the process that's complicated and that complexity can't be hidden behind just one simple button (or one CLI command). I couldn't wrap my head around git for a while when I started. Some time later I decided to write a procedure for our branching flow at work. I wanted it to cover all the common cases like: checking out a branch, squashing and rebasing, undoing things, amending commits, etc. All of which I knew was possible with Git, but I didn't feel comfortable with most of those operations and had to go to Google almost every time. So in order to put that all down in simple steps with some short explanatory comments I, obviously, was supposed to very clearly understand all of those cases myself to be ready to answer some questions and moreover to be sure that each step is a correct way to do git and it wouldn't cause any permanent damage to anybody's repo. To get that understanding I created a few nested directories with some really small text files in them and used those to actually run and inspect consequences of various git commands which took me, maybe, about two hours maximum. I've never had a single problem with git ever since. |
|
|