4 ms·
The problem is - if you're not using some feature every month you won't remember how to do it anyway when you finally need to use it. So there's little point r
by ajuc 6y ago
The problem is - if you're not using some feature every month you won't remember how to do it anyway when you finally need to use it.
So there's little point reading about exotic features upfront other than to know they exist. And which features are exotic depends on your workflow.
It would help if git interface was consistent enough to make remembering this stuff easier.
For example I never remember the exact options for git reset because I'm using it just rarely enough to forget them when I need them again.
- tankenmate 6y agoI would suggest it's far better to understand the data structures inherent in git and how those data structure changes are tracked and merged. Then almost all operations in git become clear. And as a side bonus it will probably make you a better coder.
- ajuc 6y agoHow would knowing the structure (which I already do) help me remembering what was that option called?
- jeltz 6y agoBecause most options are named after parts of the underlying structure. At least for me that makes them much easier to remember. There are some exceptions, but in general there is a logical system behind the naming.
- lsaferite 6y ago> For example I never remember the exact options for git reset because I'm using it just rarely enough to forget them when I need them again. I would argue the value is in knowing that something is possible using the `git reset` command so you know to go looking for the exact option to do what you want. And more likely you'll remember the operation if it's one you find yourself using frequently.
- gpderetta 6y ago"Education is what is left after you have forgotten all you have learned." -- someone or someone else. I forgot.