When I use git VCS, I simply work in a shell. Even more complicated branching can be resolved using git show-branch command. But this time I wanted to compare that again with gitk. Since I work on Windows I use babun which is based on Cygwin. And we know that Cygwin can actually launch gitk properly, right? Well, yes - when you configure it.
Some time ago, for about a year I've been teaching myself and newcomer company programmers about proper and efficient usage of git. Since git is a distribued VCS, which is well done for time pressure work, the "distributed" part isn't really the easiest one in such heavy context. Inbetween those teaching times I have noticed that there is much more to teach rather than only how to use some new source code management tool.
I'm not gonna explain the tool itself and tricks around it. I'd like to focus on problems around it. The following may be your checklist for practical knowledge of git. Ready for exam? Then read on.
Unity3D seems to be a great software for rapid prototype development. It certainly is but when properly used. You're alone with your prototype? It's OK but I was the other case. When it comes to collaborate there's a belief that nothing will change during the process of development. Well, the reality is that the teamwork does change a lot. If you dare to work with team using Unity, then you may find my experiences useful to you.
One fellow asked me to counter his theory if it does make any sense to work on a one-person project using git. Isn't it better to just use SVN? I disagree. And I will tell you why you have to agree with me.