3 ms·

Git is not hard, people just aren't willing to put the TIME & EFFORT to learn.

A4ET8a8uTh0 3y ago
Good grief, yes. "whatever comes next should be closer to how humans think" Hard no. I saw how people think and it is usually: this is what I think I want, but I ask for not that, but figure it out for me anyway. I will admit that articles like that make me wonder if Altman is onto something saying that AI will end us all.
chx 3y ago
My brother in Christ, why should I put in the time and effort to learn an auxiliary tool to my job? Also, let me tell you from first hand experience: I disagree with you. Let me tell you a few things about myself, just to paint a picture... I managed to gain admittance to a special math high school class with like ten kids fighting for every seat. Later I got a math teacher masters. I have been a member of Mensa for a few years. I learned Z80 assembly when I was 12 years old. Prolog when I was 15. When git came ... it was an absolute impenetrable brick wall and let me emphasize, a directed acyclic graph is not exactly an alien concept to me. It was not until Charles Duan's git tutorial that I felt I am comfortable with it. https://www.cduan.com/technical/git/ https://www.cduan.com/technical/git/ All this to say: it is hard.
- morelisp 3y ago
  If git is an auxiliary tool, your entire programming environment and language are "auxiliary tools". Today being able to persist and distribute multiple versions of source code is table stakes for being a programmer. If we're really talking about "jobs", that's probably more central than writing code - a release manager might do nothing but manage git minutia and still provide value, a programmer that can't give anyone else the code they've written provides nothing.
- bspammer 3y ago
  > why should I put in the time and effort to learn an auxiliary tool to my job? Auxiliary? I can’t speak for everyone, but VCS has to be up there as the most important development tool on my machine. I’d sooner uninstall my IDE than git. No doubt it’s hard, but sitting down and making a concerted effort for a few hours does wonders. That’s not much of an ask for something most devs use every day.
- jdiez17 3y ago
  May I ask what is your job, and what (non-auxiliary) tools have you invested time and effort in learning?
- chillbill 3y ago
  Your comment comes off as arrogant and patronizing. I don't know if that's you you meant it, but I'm going to assume so because it's fitting with your other comments. > My brother in Christ disingenuous start, this will be interesting... > why should I put in the time and effort to learn an auxiliary tool to my job? if you think git (or version control) is auxiliary tool then you have not worked on real software. I'm not saying this is you, but IF it's you (or anyone else reading): Writing side scripts and minor modifications on an existing project is not building real software, it's hobby coding, which is fine but you don't get to act like a software engineer. You're as much an engineer as someone cooking a random meal once a week is a chef. > I learned Z80 assembly when I was 12 years old. Prolog when I was 15. When git came ... it was an absolute impenetrable brick wall and let me emphasize Did you consider maybe that your "learning" of z80 asm or prolog was not complete? or possibly faux, false, fake, or gasp you're might not be as smart as you think? Or that when you were a kid you had way more time on your hands than now? The possibilities are infinite for an explanation (that is if what you're saying is true). "OMG Git is hard" is not one of the first 100 reasons that come to mind. > It was not until Charles Duan's git tutorial that I felt I am comfortable with it That's a good tutorial, but you never get comfortable with Git (or any other technical subject matter imho) until you work with it, and it will take practice and -sorry to say- humbleness in that you (or anyone else) can have hard time understanding something that many others find simple. It doesn't automatically mean it's a hard subject because you find it hard. Git is _not_ anymore hard that any other abstraction. You work hard you learn, you don't you won't.

Good grief, yes. "whatever comes next should be closer to how humans think" Hard no. I saw how people think and it is usually: this is what I think I want, but I ask for not that, but figure it out for me anyway. I will admit that articles like that make me wonder if Altman is onto something saying that AI will end us all.

chx 3y ago

My brother in Christ, why should I put in the time and effort to learn an auxiliary tool to my job? Also, let me tell you from first hand experience: I disagree with you. Let me tell you a few things about myself, just to paint a picture... I managed to gain admittance to a special math high school class with like ten kids fighting for every seat. Later I got a math teacher masters. I have been a member of Mensa for a few years. I learned Z80 assembly when I was 12 years old. Prolog when I was 15. When git came ... it was an absolute impenetrable brick wall and let me emphasize, a directed acyclic graph is not exactly an alien concept to me. It was not until Charles Duan's git tutorial that I felt I am comfortable with it. https://www.cduan.com/technical/git/ https://www.cduan.com/technical/git/ All this to say: it is hard.

morelisp 3y ago
If git is an auxiliary tool, your entire programming environment and language are "auxiliary tools". Today being able to persist and distribute multiple versions of source code is table stakes for being a programmer. If we're really talking about "jobs", that's probably more central than writing code - a release manager might do nothing but manage git minutia and still provide value, a programmer that can't give anyone else the code they've written provides nothing.
bspammer 3y ago
> why should I put in the time and effort to learn an auxiliary tool to my job? Auxiliary? I can’t speak for everyone, but VCS has to be up there as the most important development tool on my machine. I’d sooner uninstall my IDE than git. No doubt it’s hard, but sitting down and making a concerted effort for a few hours does wonders. That’s not much of an ask for something most devs use every day.
jdiez17 3y ago
May I ask what is your job, and what (non-auxiliary) tools have you invested time and effort in learning?
chillbill 3y ago
Your comment comes off as arrogant and patronizing. I don't know if that's you you meant it, but I'm going to assume so because it's fitting with your other comments. > My brother in Christ disingenuous start, this will be interesting... > why should I put in the time and effort to learn an auxiliary tool to my job? if you think git (or version control) is auxiliary tool then you have not worked on real software. I'm not saying this is you, but IF it's you (or anyone else reading): Writing side scripts and minor modifications on an existing project is not building real software, it's hobby coding, which is fine but you don't get to act like a software engineer. You're as much an engineer as someone cooking a random meal once a week is a chef. > I learned Z80 assembly when I was 12 years old. Prolog when I was 15. When git came ... it was an absolute impenetrable brick wall and let me emphasize Did you consider maybe that your "learning" of z80 asm or prolog was not complete? or possibly faux, false, fake, or gasp you're might not be as smart as you think? Or that when you were a kid you had way more time on your hands than now? The possibilities are infinite for an explanation (that is if what you're saying is true). "OMG Git is hard" is not one of the first 100 reasons that come to mind. > It was not until Charles Duan's git tutorial that I felt I am comfortable with it That's a good tutorial, but you never get comfortable with Git (or any other technical subject matter imho) until you work with it, and it will take practice and -sorry to say- humbleness in that you (or anyone else) can have hard time understanding something that many others find simple. It doesn't automatically mean it's a hard subject because you find it hard. Git is _not_ anymore hard that any other abstraction. You work hard you learn, you don't you won't.