12 ms·

I haven't had a chance to checkout Githug yet, but for me, as a former SVN user, the switch to Git was daunting. I can't really explain why, but wrapping my hea

by nantes 15y ago

I haven't had a chance to checkout Githug yet, but for me, as a former SVN user, the switch to Git was daunting. I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. For those that I point to Git now, especially those that are semi-technical, it's really useful to also point them to a nice intro. As with all new things, lowering any barrier to entry is usually a good thing.

masklinn 15y ago
> I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. Git's UI being complete shit probably helped there.
- jc123 15y ago
  For Mac, I've found this version of GitX to be really good: http://gitx.laullon.com/ http://gitx.laullon.com/
  - deleted 15y ago
    [deleted]
DrStalker 15y ago
In my case this was because Git has a model of version control that is nowhere as straightforward as SVNs and several hundred command line options without any good indication of what to do when. We also had a lot of problems with what I think of as "Linux Arrogance" - the person who took the lead on rolling out git refused to even try to help anyone not using git in a bash shell, which is an issue when all the devs are .net developers with no cygwin experience. Once you can figure out the commands you need to use git is very nice, but it's a nightmare to start and requires a big mental step backwards to teach someone with no exposure to it.
gizzlon 15y ago
"I can't really explain why, but wrapping my head around DVCS took an embarassingly long time" I guess the longer you've used a centralized approach, the more "intrenched" that way of thinking is, and the bigger the mental shift has to be. Unlearning the old can be much harder than learning the new..
obtu 15y ago
For me the lightbulb moment was seeing the data model explained (in "Git for computer scientists" for example). I'm not sure this can be conveyed in game form, and githug doesn't seem to go there. With close to a hundred commands that can be composed in various ways, teaching tasks isn't as worthwhile as teaching the principles.

by nantes 15y ago

masklinn 15y ago

> I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. Git's UI being complete shit probably helped there.

jc123 15y ago
For Mac, I've found this version of GitX to be really good: http://gitx.laullon.com/ http://gitx.laullon.com/
- deleted 15y ago
  [deleted]

DrStalker 15y ago

In my case this was because Git has a model of version control that is nowhere as straightforward as SVNs and several hundred command line options without any good indication of what to do when. We also had a lot of problems with what I think of as "Linux Arrogance" - the person who took the lead on rolling out git refused to even try to help anyone not using git in a bash shell, which is an issue when all the devs are .net developers with no cygwin experience. Once you can figure out the commands you need to use git is very nice, but it's a nightmare to start and requires a big mental step backwards to teach someone with no exposure to it.

gizzlon 15y ago

"I can't really explain why, but wrapping my head around DVCS took an embarassingly long time" I guess the longer you've used a centralized approach, the more "intrenched" that way of thinking is, and the bigger the mental shift has to be. Unlearning the old can be much harder than learning the new..

obtu 15y ago

For me the lightbulb moment was seeing the data model explained (in "Git for computer scientists" for example). I'm not sure this can be conveyed in game form, and githug doesn't seem to go there. With close to a hundred commands that can be composed in various ways, teaching tasks isn't as worthwhile as teaching the principles.