It disappoints me that so few people here read the linked article. This article talks about writing your resume in markdown and only tangentially mentioned git at all in that writing it in markdown will make it versionable. The only direct mention of github is a link to a repo that converts resumes to pdf.
Sure, but does that justify commenting on a link without even reading the content?
Keeping your resume in source control makes sense, whatever technology you end up using is completely up to you, all you really need is changelist history.
I agree with you and perhaps someone should change the title. But I am still disappointed one would see fit to dash off 50-100 words without taking the time to read the article. "Ooh, this guy pressed one of my buttons! Here we goooooooo."
My comments actually do reflect the story. The concept is cool, I get it, and it's useful. I'm commenting on the intent of the concept as well as the post title. The intent of your resume being derived from Github means that one believes your code is your "work". Maybe I'm hung up on semantics - i can see how this would be useful for augmenting and dynamically updating the resumes for a certain group.
>watching someone poke at a calculator isn't as exciting as watching slam dunks
Well, that's true. I get really excited by both math/science and basketball so I feel I'm coming from an unbiased position here: Unless you have a spectacular color man commentating on the guy using his calculator, displays of physical prowess are going to win every time in terms of 'fun to watch'. The difference is the deep sense of satisfaction that comes from learning something. This sort of positive result from an insight can continue for a lifetime, whereas, for me at least, 'my' team winning a sporting contest makes me feel good for a few fleeting moments.
Couldn't agree with you more. My SO is a PhD candidate and she doesn't know what she's missing when it comes to collaborative version control. They spend a lot of time sending around modified office docs.
Well, some people claim that tar balls and patches are a much superior source control management system than CVS. So you could say that unless you want every Joe User to master git, sending around modified office docs might not be the worst of solutions.