What does it take to make a ‘good’ developer resume?

Re:What does it take to make a ‘good’ developer resume? by jcapote on Wednesday December 16, 2009 @02:10PM (#999491)

GitHub url, big and center.

[ Parent | on HN ]

Re:What does it take to make a ‘good’ developer resume? by timr on Wednesday December 16, 2009 @03:07PM (#999597)

Yes. Because the best way to screen for an experienced developer is to make sure they're using the latest hotness in a tiny corner of the tech universe.

[ Parent | on HN ]

Re:What does it take to make a ‘good’ developer resume? by r00k on Wednesday December 16, 2009 @03:40PM (#999669)

I think you could easily substitute 'a public repository of your code and open-source contributions' for 'Github' here, but the former is shorter and conveys the same idea.

You also seem to imply that experienced developers [i]wouldn't[/i] be using a cutting-edge tool to share code. Why wouldn't they? Does 'experienced' have to mean 'curmudgeonly'?

[ Parent | on HN ]

Re:What does it take to make a ‘good’ developer resume? by timr on Wednesday December 16, 2009 @04:12PM (#999731)

"Link to your code, big and center" wouldn't have been that many more words, if that was truly what was meant.

"You also seem to imply that experienced developers [i]wouldn't[/i] be using a cutting-edge tool to share code. Why wouldn't they? Does 'experienced' have to mean 'curmudgeonly'?"

Straw man. My implication is only that it's foolish to screen for experience using a trendy tool that is adopted by only a tiny percentage of programmers.

[ Parent | on HN ]