3 ms·

I have not grokked git — it hasn't been necessary to. Understanding some of the basics, knowing enough of the commands to run, and figuring out which StackOver

I have not grokked git — it hasn't been necessary to. Understanding some of the basics, knowing enough of the commands to run, and figuring out which StackOverflow answer applies to my current situation is good enough. If I have to spend too much time knowing its internals and delving into its philosophies, then it is not a useful tool that lets me get on with my tasks.

JKCalhoun 4y ago
Agree, sort of. I sort of get git but have never grokked it, for sure. But I don't think I should need to fully understand its internals for it to be "grokkable", an elegant thing could still be grokkable regardless. It's possible though that the tasks: diffing, branching, merging, rebasing, tagging, etc., are too elusive for "elegance", ha ha. I might add though that simple diffing, branching, merging I do more or less grok. Perhaps if git had stopped there, like my understanding did, I would feel more comfortable with it ... imposed limitations be damned. I suppose in fact I only use git in this limited capacity anyway. It's only when someone else on the team does something clever (or I screw something up)....
rgoulter 4y ago
Kinda. I wouldn't be able to tell you too much about the internals of VSCode. The 'trouble' with git is, though, that what happens when you run the wrong command can vary from "easy to fix" all the way to "you just lost your work, you shouldn't have run that command". Which means you need to either be very careful anytime you run git, or you need to learn more about git to avoid the footgun aspects of it.
- lijogdfljk 4y ago
  It's kinda sad though because off the top of my head i suspect it's really difficult to actually lose your work. Ie between the fact that the content store stores.. well, all content, until it's GC'd, and the obvious reflog, you can almost always get back your data. The downside to this though is the type of novice most likely to make a mistake in "losing" their data will also not know how to recover their data.
  - rgoulter 4y ago
    > it's really difficult to actually lose your work If it's been checked into a commit, sure. But if you discard changes which haven't been checked in, then the work is lost.

JKCalhoun 4y ago

Agree, sort of. I sort of get git but have never grokked it, for sure. But I don't think I should need to fully understand its internals for it to be "grokkable", an elegant thing could still be grokkable regardless. It's possible though that the tasks: diffing, branching, merging, rebasing, tagging, etc., are too elusive for "elegance", ha ha. I might add though that simple diffing, branching, merging I do more or less grok. Perhaps if git had stopped there, like my understanding did, I would feel more comfortable with it ... imposed limitations be damned. I suppose in fact I only use git in this limited capacity anyway. It's only when someone else on the team does something clever (or I screw something up)....

rgoulter 4y ago

Kinda. I wouldn't be able to tell you too much about the internals of VSCode. The 'trouble' with git is, though, that what happens when you run the wrong command can vary from "easy to fix" all the way to "you just lost your work, you shouldn't have run that command". Which means you need to either be very careful anytime you run git, or you need to learn more about git to avoid the footgun aspects of it.

lijogdfljk 4y ago
It's kinda sad though because off the top of my head i suspect it's really difficult to actually lose your work. Ie between the fact that the content store stores.. well, all content, until it's GC'd, and the obvious reflog, you can almost always get back your data. The downside to this though is the type of novice most likely to make a mistake in "losing" their data will also not know how to recover their data.
- rgoulter 4y ago
  > it's really difficult to actually lose your work If it's been checked into a commit, sure. But if you discard changes which haven't been checked in, then the work is lost.