5 ms·
Apparently we have very different opinions as to what constitutes elegant. I would call the example messy and confusing.
by mrweasel 11y ago
Apparently we have very different opinions as to what constitutes elegant. I would call the example messy and confusing.
- laurent123456 11y agoYeah I think it's due to the (mis)use of quoted text to indent some paragraphs, which means there are vertical bars all over the place. The additional horizontal lines don't help much either. I think if he removes that it would look relatively clean, like a README.md on GitHub. Here's the source of the example by the way: https://gist.githubusercontent.com/awalGarg/a8e97b27b249f2c94f8e/raw/09e63fd69f2288cd631a492d392e8d114af7a432/res.md https://gist.githubusercontent.com/awalGarg/a8e97b27b249f2c9...
- awalGarg 11y agoHmm, well, noted :) If you could point out some specific elements in the rendered version though, like "not enough spacing" or "that h3 should be an h2", that'd be extremely helpful!
- mrweasel 11y agoIt's not really that simple. I'm not trying to be dick about, because I do think that resumes from markdown is a good idea. The grey borders/lines, they need to go. They serve no purpose. Contact information goes on top, not buried under the profile. Technologies, can go after the "job description". It makes sense to list them in relation to the jobs though. Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. Writing and favourites can go, unless you a famous blogger, but then I would just list it as a job. The entire resume takes up to much space. It's country specific, I know, but I think it needs to fit on one A4 page. Personally, I just don't like the layout, sorry.
- awalGarg 11y ago> The grey borders/lines, they need to go. They serve no purpose. Completely agree. While I think it is fair to put a bit of blame of Github's bad rendering (the same markdown looks much better in stackedit's rendering, for instance [1]), but I'd still see how can I preserve the grouping without blockquoting things. I can see the reasoning for rest of the points as well, but to each his own :) [1]: https://stackedit.io/viewer#!url=https://gist.githubusercontent.com/awalGarg/a8e97b27b249f2c94f8e/raw/09e63fd69f2288cd631a492d392e8d114af7a432/res.md https://stackedit.io/viewer#!url=https://gist.githubusercont...
- laurent123456 11y agoRather than creating the markdown for a specific renderer, I think you should focus on creating markdown that can be easily read and edited - so no "######" headings, no quoted text or horizontal lines, basically no clutter. Then how it appears in HTML can be tweaked by the renderer and via CSS. Also I assume clean markdown would generally look better in most renderers.
- mrweasel 11y ago>the same markdown looks much better in stackedit's rendering Link to that one as the example then ;) I think it's down to different markets wanting different things. A cool project, but maybe not so useful, would be a resume generator that from one data source (in Markdown perhaps) could generate resumes in the "correct" form for Europe, India, the US and so on.
- awalGarg 11y agoNoted. I have added links to various rendered forms in the readme: https://github.com/awalGarg/cv-maker#example https://github.com/awalGarg/cv-maker#example
- rifung 11y ago> Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. I assume you mean "no" instead of "know". But more on point, are you sure this is true? I have heard many companies (Google is one) look highly on projects you made which are very popular.
- frostirosti 11y agoThose look absolutely terrible. If someone sent me that, I'd just throw it away. I'd think it was interesting, but totally unreadable.
- protomyth 11y ago> I'd just throw it away Do check your local laws for retention of resumes / applications before throwing it away.
- 1812Overture 11y agoWhere is this a thing?
- laumars 11y agoAgreed. Plus the source is an even bigger mess, which negates one of the biggest benefits of using markdown in the first place (ie, if you can't easily parse it in Notepad then you might as well just create the document in HTML, ODF, DOCX or, better yet, send it in as a PDF. I think even the joke JSON resume was easily to parse and the JSON format wasn't intended to be human readable / editable.
- aloisdg 11y agoWhy JSON resume is a joke?
- magic_beans 11y ago"the JSON format wasn't intended to be human readable / editable" Recruiters, not developers, generally read resumes. They are not used to reading JSON and it is hard for them.
- scrollaway 11y agoYou realize the idea of JSON resume isn't "Write your CV in json and send that to your employer"... right? It's actually quite sound: JSON Resume wants to standardize CV fields to improve compatibility between tools, ease conversion, ease theming and such. It's a joke because it sounds good on paper but the execution is awful. I tried it out and the resulting CVs are look completely unprofessional, except they took three times as much effort.
- BHSPitMonkey 11y agoYou can render it any way you want to. The example themes aren't the point.
- yesco 11y agoYeah I still think its a good idea, its nice to have all that information stored somewhere. If its in json then I can use it in a program or if I want to do it manually then I can read the json file directly. Definitely better then the scribbles in my notebook. I don't really understand what part of it constitutes a "joke".
- thenipper 11y agoEchoing what a lot of other folks are saying the design of the resume isn't great. Note I don't work hiring programmers but a portion of my job is in recruiting. - It is hard to scan. Often times a recruiter will be scanning through 100+ resumes. The fact that it doesn't follow the 'standard' format of resumes makes me have to break out of my usual pattern of how I'd scan a resume. - I don't care about what you're reading. Sorry but it's true. I kind of don't care about your blog posts. I'm not going to click on the links though. I might if you make it past the initial screen. - I do like the skill sets under each job. That's handy. I don't care for 'favorites'. Just tell me what you know how to do preferably in a more concise manner. - Don't give me three emails on how to contact you. I'm a tired stressed out recruiter I don't wanna play a game on which email I think you'll respond to. "Don't make me think" is just as valid as it is for hiring as it is for web design. Help the recruiter make the case as to why you're a great hire. I don't think that the non-standard formatting helps with that.
- cpt1138 11y agoSorry this reply screams "I don't care, I'm tired, I'm stressed, don't make me think." What exactly is your value here? All you're doing is fitting a cog in the machinery. Since my impression is that a good developer can deal with any situation necessary, I never understood the laundry list of technologies way of fitting a candidate to a "good hire." We know this is the reality of recruiters. Maybe on HN do a better job of selling the industry of tired, stressed, people that don't care working to fill a slot.
- coldtea 11y ago>Sorry this reply screams "I don't care, I'm tired, I'm stressed, don't make me think." Well, if you're expecting anything else from a recruiter being send your resume you'll be in for a hard surprise. The inverse is "I couldn't put in the time to make my CV tidy and intuitive, but you'll have to soldier thru it, because I have the mistaken opinion that I'm a unique snowflake and you don't get hundreds of them". In fact, "don't make me think" is a GREAT advice for anything you want others to read/try/adopt/buy. http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758 http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/032134... >Since my impression is that a good developer can deal with any situation necessary, I never understood the laundry list of technologies way of fitting a candidate to a "good hire." Even if a good C++ game developer could switch to Javascript front-end development if needed (to give an extreme example), the time it takes to have them familiar with the relevant stack is better spent hiring someone already familiar. And, it's kind of obvious -- both can be just as good. It's just the second is also ready to hit the ground running on the stack a company uses. And, of course, just because someone "can deal with any situation necessary" doesn't mean they'd like to. Some programmers like to program in X or Y languages (or language families), others like building Z or K kind of programs. Just because someone could switch from Haskell to Ruby or from scientific programming to CRUDs doesn't mean they'd also like to. In this case the "laundry list" serves as a way to match hires that are interested in the specific things the company works with.
- rplnt 11y agoThis is what grabbed me in the title even before looking at the link. Someone calling their own creation elegant. I just found it weird. Like someone saying "I made this good game". Of course that's what you would (should) say to the customers, but here it doesn't fit somehow.
- odonnellryan 11y agoI feel it is a start.