7 ms·

Hey guys, we weren't actually ready for a lot of eyes to see this project. We were hoping to keep it small and get some feedback on important decisions about th

Hey guys, we weren't actually ready for a lot of eyes to see this project. We were hoping to keep it small and get some feedback on important decisions about the project's trajectory. The plan is to create a standard that developers worldwide are comfortable enough with to build upon. To give the standard some traction, we have built tools to export to other formats such as pdf, txt and doc. We also thought it would be cool and useful to have an NPM like system for resumes. So we built a CLI heavily inspired by NPM, to init and publish your resume to the jsonresume.org registry. The themes right now are in bad shape, and we are looking for designers who would love to jump in during the early stages. We are thinking of building a theming version manager on top of NPM to take advantage of versions/distribution and also allow theme developers to implement their theming systems however they like (erb, mustache, md etc). All the code is open source and available at -> http://github.com/jsonresume http://github.com/jsonresume Theme developers should be looking at the resumeToHTML repo -> http://github.com/jsonresume/resumeToHTML http://github.com/jsonresume/resumeToHTML People with comments about the standard semantics and structure are encouraged to post their ideas to Github issues. -> http://github.com/jsonresume/resume-schema http://github.com/jsonresume/resume-schema We also want to formalize the standard a lot more over the coming weeks. If the project can be pulled off professionally and driven by the community, we believe that working with resumes will be fun! Edit: Here are some of the reasons why I personally think JSON resumes will improve HR. (trying to figure out bullet points) - Better searching and filtering than PDF/doc. Making recruiting a tad easier. - Applying themes will be a lot easier. - Applying for jobs will be easier. Instead of filling out complex forms over and over again services might start allowing you to auto-fill with your JSON resume. - There are many services that ask for your career history such as LinkedIn, Angel.co etc. These could be autopopulated or synced with your master copy. - You can update your resume programatically so Github projects can be inserted and any other online certificates that you might want automatically added to your resume like Mozilla Open Badges -> http://openbadges.org/ http://openbadges.org/ - The comment section suggests that lots of innovation could arise from it. ---------- Make sure you try the CLI! sudo npm install -g resume-cli

pserwylo 12y ago
I would just like to say that I think that this is a great idea(despite agreeing with others here that XML + XSLT would seem like a more logical choice). I hope it gets some traction in the long run. I've posted an issue on github [0][1] mentioning that "firstName" and "lastName" is probably not a good representation of names. I don't actually know what the solution is, but this article [2] gives some great reasons why we tend to make incorrect assumptions about peoples names, which have the possibility of excluding some people form our tools based on their name alone. [0] - https://github.com/jsonresume/resume-schema/issues/4 https://github.com/jsonresume/resume-schema/issues/4 [1] - It seemed like an appropriate place to comment. Please let me know if there is somewhere else you'd prefer such comments. [2] - http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...
- keehun 12y ago
  I agree with the names. Even just the ordering of first/last name can be difficult. I come from Korea where last name always comes before the first name in a formal setting. Perhaps you should just require "full name" which the author of the resume would decide for him or herself.
  - chii 12y ago
    or, have both fields, which the author needs to fill in. This makes it easy to parse the data, but also makes it readable by humans, by separating it into different fields, for different purposes.
  - matthewrudy 12y ago
    Facebook takes a "family name" and a "given name", and asks you which order to display them, right?
    - TazeTSchnitzel 12y ago
      Facebook also supports middle names too, though.

pserwylo 12y ago

I would just like to say that I think that this is a great idea(despite agreeing with others here that XML + XSLT would seem like a more logical choice). I hope it gets some traction in the long run. I've posted an issue on github [0][1] mentioning that "firstName" and "lastName" is probably not a good representation of names. I don't actually know what the solution is, but this article [2] gives some great reasons why we tend to make incorrect assumptions about peoples names, which have the possibility of excluding some people form our tools based on their name alone. [0] - https://github.com/jsonresume/resume-schema/issues/4 https://github.com/jsonresume/resume-schema/issues/4 [1] - It seemed like an appropriate place to comment. Please let me know if there is somewhere else you'd prefer such comments. [2] - http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...

keehun 12y ago
I agree with the names. Even just the ordering of first/last name can be difficult. I come from Korea where last name always comes before the first name in a formal setting. Perhaps you should just require "full name" which the author of the resume would decide for him or herself.
- chii 12y ago
  or, have both fields, which the author needs to fill in. This makes it easy to parse the data, but also makes it readable by humans, by separating it into different fields, for different purposes.
- matthewrudy 12y ago
  Facebook takes a "family name" and a "given name", and asks you which order to display them, right?
  - TazeTSchnitzel 12y ago
    Facebook also supports middle names too, though.