4 ms·
Learning "recipes" on the internet and copy pasting commands is a sure way to mess something up and could bring a lot of frustration. You only need to spend a f
by rootlocus 9y ago
Learning "recipes" on the internet and copy pasting commands is a sure way to mess something up and could bring a lot of frustration. You only need to spend a few hours to understand how git works underneath to avoid any of that.
- ptero 9y agoYou should not have to learn the internals of any decent source control system to use it in a way that does not lead to a mess. An overview of usage principles and examples should be enough and should provide enough insight to search for more information if needed. User level documentation should be sufficient for user actions. If someone wants to learn internals, great; but this should be an option, not a requirement.
- rootlocus 9y agoLots of "should"s, but we're talking about advice on using git, not "any decent source control system". This is a problem I see with people not understanding git. They treat it like they think it should be treated. Like it or not, that's not going to work for git. You don't give python advice to a C++ developer, regardless of how much you'd like C++ to be like python.
- taeric 9y agoThis logic also works on computers. Or, well, anything. You'd be surprised at just how useful people can find things while still making a mess of them. So, yes, if you have the time, learn the internals. But no, that is not in any way a prerequisite. Nor should it be.
- rootlocus 9y ago> You'd be surprised at just how useful people can find things while still making a mess of them. You mean like this? http://www.thisiscolossal.com/2017/12/tatsuo-horiuchi-excel-artist/ http://www.thisiscolossal.com/2017/12/tatsuo-horiuchi-excel-...
- taeric 9y agoI wouldn't have thought of that, but yes. :) Most of my inspiration nowadays comes from my kids.