3 ms·
It's hard because nobody thinks of it as a part of their job. Like coding is to some people, git is often a thing that you just have to do. So then you don't l
by lordnacho 4y ago
It's hard because nobody thinks of it as a part of their job. Like coding is to some people, git is often a thing that you just have to do.
So then you don't learn how it really works, and you get weird problems because you never formed the right model in your mind.
It's also the case that there's a few commands you use a lot, but a lot of commands that you reach for only in specific cases. This creates the impression that it's too complicated, because as soon as you go off road you get stuck.
- fragmede 4y agoTotally, which results in the "memorize this list" git XKCD. https://xkcd.com/1597/ https://xkcd.com/1597/ They have classes for compilers in school, they should have a 1 week class on source control because git makes a lot of sense if you understand the underlying data structures.
- pessimizer 4y agoMy problem is that sometimes I have to "drop" things, sometimes I have to "delete" things, sometimes I have to "--delete" things, sometimes I have to "-d" things and sometimes I have to "-D" things. There's nothing wrong with the architecture or model, it's the syntax for me.
- 1ark 4y agoMore interview questions about git rather than silly fizzbuzz puzzles.