Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JSON Resume – 5th Birthday and New Features

jsonresume.org

Post reply on HN
Print view View original

41–50 of 58 posts

Re: JSON Resume – 5th Birthday and New Features

#41

Post by C1sc0cat »

thomasfromcdnjs wrote: post #13
goblin89 wrote: post #7

Instead of going with an ad-hoc schema, I wish JSON Resume built on top of data structures standardized by Schema.org. They cover most of the concepts required— https://schema.org/Person , https://schema.org/skills , https://pending.schema.org/knowsAbout , the list goes on. For concepts not covered by Schema.org (I spotted only one, “interests”) the project could implement custom extensions until they are adopted by…

I personally don't disagree, we've always thought it best to leverage other peoples work first. Though one of the largest discussions we had on the specification was the definition of what a name was -> https://github.com/jsonresume/resume-schema/issues/4 After everyone's input, we decided to just opt for one field `name` because simply first/last/family name does not work across cultures. When we looked at schema.or…

I seem to recall X.400/X.500 did a lot of work on how to represent names.

Maybe if you could find a copy of those specs pity that the ISO and ITU where always so restrictive and dam expensive.

Re: JSON Resume – 5th Birthday and New Features

#42

Post by michael-ax »

matthewbauer wrote: post #33
pknopf wrote: post #12

Pro tip, just creating your own schema. Tailor it to your theme. Here is my resume (as YAML): https://github.com/pauldotknopf/resume/blob/staging/resume.y... This file is consumed and used in a very small ad-hoc project, specifically for my format: https://github.com/pauldotknopf/resume/blob/staging/statik-r... Here is the final result: https://resume.pknopf.com/ Easy maintenance. Maximum flexibility. Low tooling.

LaTeX + ORG mode is an easy way to get some literate programming features while also still using a real typesetting engine. You can reuse my setup here: https://github.com/matthewbauer/resume

Thank you! and thanks for not forcing bibtex into it.

Re: JSON Resume – 5th Birthday and New Features

#43

Post by jjjbokma »

pknopf wrote: post #12

Pro tip, just creating your own schema. Tailor it to your theme. Here is my resume (as YAML): https://github.com/pauldotknopf/resume/blob/staging/resume.y... This file is consumed and used in a very small ad-hoc project, specifically for my format: https://github.com/pauldotknopf/resume/blob/staging/statik-r... Here is the final result: https://resume.pknopf.com/ Easy maintenance. Maximum flexibility. Low tooling.

YAML + mostly markdown: https://github.com/john-bokma/resume-pandoc

Creates LaTeX or PDF.

Re: JSON Resume – 5th Birthday and New Features

#44

Post by frenchyatwork »

wongarsu wrote: post #31
bvda wrote: post #29

Earlier quoted context omitted.

Is there any reason not to use a singular field for this? It seems so much simpler to just give the user one input field and it would cover all scenarios.

Apparently a single field works fine in a resume builder. But consider a more complex app that does all of the following: display the name in various lists, has a detail view on that user, greets the user, talks about the person in third person (a report or similar). In each of those cases you ideally want to treat the name differently. Even in English the detail view might show George Walker Bush Jr (the legal name…

I would imagine that most software would work perfectly fine with two values:

* What do you want to be called?

* (for some cases) What is your legal name?

Trying to decide what level of formality and/or honorifics is appropriate in a specific case seems insane. Just let the user decide.

Re: JSON Resume – 5th Birthday and New Features

#45

Post by ilaksh »

heinrichhartman wrote: post #37

Aside: > resume export resume.pdf (Currently broken, help needed) https://jsonresume.org/getting-started/ Any news here? Still puzzling to me, how hard it is to generate PDF documents. I assume this is not using Latex, since that would be a gigantic dependency to pull in. What is/was jsonresume using? Why did it break? PS: Also pdf export on wikipedia has been broken for years now. Seems to be a hard problem. Any inf…

https://github.com/jsonresume/resume-cli/pull/294

Re: JSON Resume – 5th Birthday and New Features

#46

Post by ilaksh »

elcomet wrote: post #39

I wish it was called yamlresume.org instead of jsonresume.org. Json is not designed for humans.

yamlresume.org is available.

There are multiple projects on GitHub that generate resumes from yaml.

The new concept is a lambda function that pulls from a gist. It would not be very hard to do something similar with yaml.

Re: JSON Resume – 5th Birthday and New Features

#47

Post by hombre_fatal »

agumonkey wrote: post #26
irrational wrote: post #25

It took me way too long to realize resume meant résumé (written summary of my experiences) instead of resume (to continue)! I was thinking JSON Resume was the next version of JSON, maybe adding the ability to have comments in JSON.

Or lazy loaded json as stream of objects

Well, you can already parse JSON SAX-style. Or with newline delimiters.

Re: JSON Resume – 5th Birthday and New Features

#48

Post by [deleted] »

toyg wrote: post #6

Uh, there was already an XML format for this, I remember doing my CV with it. Nobody ever asked to see it or use it, so I stopped updating it. I learnt a few years later that some HR/recruiter systems do use it, behind the scenes, to talk to each other, they just never surface it. Why would this surface more often...? The HR industry is not made by coders, they live in MSWord and GDocs.

[deleted]

Re: JSON Resume – 5th Birthday and New Features

#49

Post by vcavallo »

heinrichhartman wrote: post #37

Aside: > resume export resume.pdf (Currently broken, help needed) https://jsonresume.org/getting-started/ Any news here? Still puzzling to me, how hard it is to generate PDF documents. I assume this is not using Latex, since that would be a gigantic dependency to pull in. What is/was jsonresume using? Why did it break? PS: Also pdf export on wikipedia has been broken for years now. Seems to be a hard problem. Any inf…

maybe have a good css sheet for print styles and encourage people to print -> save as pdf?

Re: JSON Resume – 5th Birthday and New Features

#50

Post by stevesimmons »

frenchyatwork wrote: post #44
wongarsu wrote: post #31

Earlier quoted context omitted.

Apparently a single field works fine in a resume builder. But consider a more complex app that does all of the following: display the name in various lists, has a detail view on that user, greets the user, talks about the person in third person (a report or similar). In each of those cases you ideally want to treat the name differently. Even in English the detail view might show George Walker Bush Jr (the legal name…

I would imagine that most software would work perfectly fine with two values: * What do you want to be called? * (for some cases) What is your legal name? Trying to decide what level of formality and/or honorifics is appropriate in a specific case seems insane. Just let the user decide.

> Trying to decide what level of formality and/or honorifics is appropriate in a specific case seems insane.

I once worked at an Australian bank that had a massive SQL function, prob 500+ lines long, for getting the salutation right in mailshots. As well as the usual Mr/Mrs/Dr/etc options, it had decades worth of special cases, largely derived from complaints from VIPs.

e.g. Retired navy officers, professors emeritus, former Members of Parliament, archbishops and rabbis, a rather pompous husband of a female Lord Mayor,...

Post reply on HN