[solomatov]

>+ Learn how to use git productively in a team environment (this means no more working directly out of master). This is a good resource to that end: http://nvie.com/posts/a-successful-git-branching-model/

But why everybody should use this kind of branching model? Branches have their overhead, namely time spent merging after several days of work.

[hamburglar]

Saying a person doesn't know how to use git productively based on their personal github projects is simply ridiculous. Nearly everything I put on github is experimental wankery presented as a curiosity, not a release. It has nothing whatsoever to do with my ability to use git productively. I can only conclude that anybody who would make this criticism has a strong "everyone should be just like me" value and is probably not someone I'd want to work with.

[jhildings]

>Saying a person doesn't know how to use git productively based on their personal github projects is simply ridiculous. Nearly everything I put on github is experimental wankery presented as a curiosity, not a release.

And also a method for quickly sharing code or projects with friends, instead of storing them on a server that requires FTP/SSH for access. Then everyone can just browse things in an easy way

[gr3yh47]

>Saying a person doesn't know how to use git productively based on their personal github projects is simply ridiculous.

thank you. i agree.

[shayanjm]

If you have your personal projects listed in your resume - you'd better make damn sure they are at least 80% polished and _SHOW OFF_ your skills. If they are not/do not, don't list them in your resume or make them private.

[solomatov]

I completely agree with you.