4 ms·
(author here) You're right; I considered this aspect, but thought it was more important to preserve the flexibility to e.g. name sections whatever I want, or o
by graphene 12y ago
(author here)
You're right; I considered this aspect, but thought it was more important to preserve the flexibility to e.g. name sections whatever I want, or order them however I want. Ultimately I see the final document (html or pdf) as primarily intended for human, not computer consumption.
- jimktrains2 12y ago> Ultimately I see the final document (html or pdf) as primarily intended for human, not computer consumption. Which for a resume isn't a bad assumption. Additionally, if I choose to use something semantic to define the resume, this is a wonderful way to format it nicely:)
- graphene 12y agoI agree, the two approaches are complementary, and it might even make sense to write a tool to convert from json to markdown, in order to take advantage of the formatting.
- vidarh 12y agoIn pretty much every position where I've interviewed developers, the resumes have arrived "ready mangled" by recruiters that have cut and pasted it into word docs with their own headers and the like, so my assumption would be like yours, that it's for human consumption. Furthermore I'd assume that the chances of any semantic markup surviving past the first meeting with a recruiter is pretty close to zero.