4 ms·
Three words against git: Detached Head State I view git as a sort of shibboleth. You can't really understand how git works unless you understand trees as a da
by fsk 12y ago
Three words against git: Detached Head State
I view git as a sort of shibboleth.
You can't really understand how git works unless you understand trees as a data structure. That excludes all but the hardcore types.
Some designers and CSS experts need to use source control, but Git is too complicated for them.
Once you get a detached head state or corrupted repo, then you need a git expert to clean things up. I once committed while in a detached head state, and so git ate my changes and I had to reflog to recover them. That is just insulting.
At my job, I work with some designers now, and they always leave the test server in a detached head state.
But when I switched from the GitHub client (yuck) to the SourceTree client, most of my concerns went away.
- tekacs 12y ago> unless you understand trees as a data structure Well unless you understand DAGs, more like? Which is somewhat more unhelpful. :P (given that merge commits have multiple parents)
- allemagne 12y ago>You can't really understand how git works unless you understand trees as a data structure. That excludes all but the hardcore types. DAGs and BSTs are taught in second year undergraduate classes where I'm at. What's hardcore about them? Serious question.
- to3m 12y agoNon-programmers tend not to have taken undergraduate computer science classes!