Comment by thomasfromcdnjs | Hacker News Reader

Comment by thomasfromcdnjs | Hacker News Reader

Parent Full thread

thomasfromcdnjs

Json Resume is still going strong. I am one of the founders, I try to do a couple major maintenance periods per year. Currently I am working on updating all the community projects built, still got quite a few to add but currently there is -> https://jsonresume.org/projects/

I think over 3k+ people use the new Gist hosting. (In our old hosting we had around 10k resumes. Not including those who by pass the free community hosting)

===

On a personal note, I've loved having my resume in a standard;

- Depending on what type of company/person I am applying to I will change my theme on the fly. (Startup vibes I will make it look hipster, if it's a more formal role I will use a simple black and white theme)

- I use to lose my most recent resume constantly, having it in a Gist called resume.json that I just edit seems to have solved that for me.

- Hopefully one day a standard will get integration adoption so I can just upload my resume.json and not have to fill out the same form fields a hundred times.

List of resume.json's on gist.github.com -> https://gist.github.com/search?l=JSON&o=desc&q=resume.json&s...

Hey thanks for maintaining this project! I have been using it this round of applications and it’s just so much more convenient than trying to edit a historical doc(x) file with a rotating cast of word editors over the years.

Hey! Appreciate this product a lot, this has been my go-to with a One Page theme for years now :)

Why JSON? Why not YAML or something more easily editable by a human?

Could of went either way really, YAML is a superset of JSON, so in theory, you can switch between them at any time.

I think we wanted JSON at the time because it just relied on less extra packages when working inside of the JS ecosystem.

So yeah, if anyone wants to make a resume.yaml, we only need to add an extra step to convert it to json for them to use any of the tooling.

Fair. I guess the reason I asked is because YAML is a little easier to play with for humans, especially since some sections need things like new lines among other things. Doing a YAML text block is easier to read and write than JSON's quoted string with new lines replaced with `\n`.

Reply on news.ycombinator.com