4 ms·

The author is of course absolutly correct in every respect but I can't help thinking that he's is one of those devs who struggles terribly with programming. Thi

The author is of course absolutly correct in every respect but I can't help thinking that he's is one of those devs who struggles terribly with programming. This type tends to give up eventually. Sometimes after years of work. His struggle to learn git is telling. Sure git is complex but it's not quite that hard for many of us. This leads to bewildered frustration with programming and a general distrust of all programs.

brudgers 12y ago
Vikram Chandra is a writer. https://en.m.wikipedia.org/wiki/Vikram_Chandra_(novelist) https://en.m.wikipedia.org/wiki/Vikram_Chandra_(novelist)
woah 12y ago
Git is pretty easy to learn, mostly you'll only ever use about 5 commands. There's the ninja voodoo stuff, but you can look the up on stack overflow.
- stinos 12y ago
  Git is pretty easy to learn No generalizing please, this is not true everyone, maybe not even for a majority of it's users. I know enough people which after having used it for months still do not really grasp it. Sure, they can sort of get around with the 5 commands they need, but anything slightly beyond that and they are lost.
- Too 12y ago
  The problem is that everyone will need the ninja voodo stuff eventually, most often during the learning phase of git when you easily hit some of the land mines and have to revert. Like when you commit to a detached head, change branch and loose one week of work. After we switched to git at work every single one of us, without exception, did this kind of mistake at least once the first month. Aborting "rebase in progress" isn't exactly easy either if something went wrong during the merge.
  - icebraining 12y ago
    Like when you commit to a detached head, change branch and loose one week of work. Git doesn't lose your commits that easily; they're still there, you just need to find them: http://gitready.com/intermediate/2009/02/09/reflog-your-safety-net.html http://gitready.com/intermediate/2009/02/09/reflog-your-safe...
    - Too 12y ago
      I know you don't loose the commits but the initial feeling is that you do. My point was that to get them back you must use the ninja voodo tricks.
rntz 12y ago
> This leads to bewildered frustration with programming and a general distrust of all programs. I think this is perhaps a more honest attitude to the state of programming today than those of us who have managed to master it are willing to permit ourselves. We suffer from the sunk cost fallacy: we are tempted to imagine that the complexity we have mastered is necessary, because if it were not, then we would feel our time spent learning it had been wasted.

brudgers 12y ago

Vikram Chandra is a writer. https://en.m.wikipedia.org/wiki/Vikram_Chandra_(novelist) https://en.m.wikipedia.org/wiki/Vikram_Chandra_(novelist)

woah 12y ago

Git is pretty easy to learn, mostly you'll only ever use about 5 commands. There's the ninja voodoo stuff, but you can look the up on stack overflow.

stinos 12y ago
Git is pretty easy to learn No generalizing please, this is not true everyone, maybe not even for a majority of it's users. I know enough people which after having used it for months still do not really grasp it. Sure, they can sort of get around with the 5 commands they need, but anything slightly beyond that and they are lost.
Too 12y ago
The problem is that everyone will need the ninja voodo stuff eventually, most often during the learning phase of git when you easily hit some of the land mines and have to revert. Like when you commit to a detached head, change branch and loose one week of work. After we switched to git at work every single one of us, without exception, did this kind of mistake at least once the first month. Aborting "rebase in progress" isn't exactly easy either if something went wrong during the merge.
- icebraining 12y ago
  Like when you commit to a detached head, change branch and loose one week of work. Git doesn't lose your commits that easily; they're still there, you just need to find them: http://gitready.com/intermediate/2009/02/09/reflog-your-safety-net.html http://gitready.com/intermediate/2009/02/09/reflog-your-safe...
  - Too 12y ago
    I know you don't loose the commits but the initial feeling is that you do. My point was that to get them back you must use the ninja voodo tricks.

rntz 12y ago

> This leads to bewildered frustration with programming and a general distrust of all programs. I think this is perhaps a more honest attitude to the state of programming today than those of us who have managed to master it are willing to permit ourselves. We suffer from the sunk cost fallacy: we are tempted to imagine that the complexity we have mastered is necessary, because if it were not, then we would feel our time spent learning it had been wasted.