4 ms·

I have been using Git since college and for a few years since I began my job, can't say I have had any problem that I couldn't find a solution for oneline. Plus

I have been using Git since college and for a few years since I began my job, can't say I have had any problem that I couldn't find a solution for oneline. Plus, I use Github Desktop now, so I do not have to worry about the pesky commands as much as I would have earlier.

alkonaut 4y ago
> any problem that I couldn't find a solution for oneline. That could still be the pulling my hair situation he mentions. Having too Google or even being up a documentation is a failure for a tool like this. When I argue that git is bad it’s “unintuitive” I mean. I have to RTFM after years of use. I does the job but it’s a shit UX. It’s like getting in your car and having to Google how to put it in reverse, for the 10th time, after driving it for 10years.
- anshumankmr 4y ago
  Yes, I see. I don't mind doing it, cause anyway I google the solution to a bunch of problems I face at work every other day. My tolerance for Googling solutions would is very high. But it might not be the same for him, I suppose. And it would definitely vary from person to person..
saghm 4y ago
> I have been using Git since college and for a few years since I began my job, can't say I have had any problem that I couldn't find a solution for oneline I agree with this, but I don't think that's strong enough evidence to conclude that git's interface isn't clunky. Being able to find solutions online is worse than being able to figure them out on my own, and being able to figure them out on my own is worse than just not having them. Obviously no software will ever be free from issues, and most can have some sort of issue that isn't able to be figured out without searching online, but I'm not convinced that git does a particularly good job about minimizing the potential for these types of issues. Overall, I've learned to use git effectively for my work, and I've often helped teammates when they run into a git issue they don't understand, but this is mostly due to the fact that I've run into issues enough before to know how to avoid some of the pitfalls.

alkonaut 4y ago

> any problem that I couldn't find a solution for oneline. That could still be the pulling my hair situation he mentions. Having too Google or even being up a documentation is a failure for a tool like this. When I argue that git is bad it’s “unintuitive” I mean. I have to RTFM after years of use. I does the job but it’s a shit UX. It’s like getting in your car and having to Google how to put it in reverse, for the 10th time, after driving it for 10years.

anshumankmr 4y ago
Yes, I see. I don't mind doing it, cause anyway I google the solution to a bunch of problems I face at work every other day. My tolerance for Googling solutions would is very high. But it might not be the same for him, I suppose. And it would definitely vary from person to person..

saghm 4y ago

> I have been using Git since college and for a few years since I began my job, can't say I have had any problem that I couldn't find a solution for oneline I agree with this, but I don't think that's strong enough evidence to conclude that git's interface isn't clunky. Being able to find solutions online is worse than being able to figure them out on my own, and being able to figure them out on my own is worse than just not having them. Obviously no software will ever be free from issues, and most can have some sort of issue that isn't able to be figured out without searching online, but I'm not convinced that git does a particularly good job about minimizing the potential for these types of issues. Overall, I've learned to use git effectively for my work, and I've often helped teammates when they run into a git issue they don't understand, but this is mostly due to the fact that I've run into issues enough before to know how to avoid some of the pitfalls.