[jsaxton86]

As mentioned several times, Github is not your resume. At the very least, it's not mine. Sure, I have a github profile, but the little side projects there don't really have anything to do with my professional work (most recently, data deduplication and video processing).

Also, LaTeX can produce much, much better resumes than markdown. Here's a link to my (extremely dated) resume using the moderncv template: http://jsaxton.com/resume.pdf

It's great for a number of reasons:

1: It immediately gets the attention of the hiring manager, since it looks way better than the typical MS Word resume.

2: It's really easy to edit. If I want to add an item, I just add "/item Did X". It's great.

3: It's plaintext, so you can throw it in git, which is really nice. Since I don't want the public to know if I'm updating my resume, I keep my resume in a private git repository (the same private repo where I keep all my Coursera work).

[pearjuice]

I am sorry but that CV needs some spacing. The font rendering might be top notch but it's way too cramped.

[X-Istence]

I don't mind the public knowing I am updating my resume, I too use moderncv and love how nice my resume looks with very little work.

What you mentioned about people liking the way the resume looks is absolutely true, but I still get a lot of people that ask for it in Word format, especially recruiters. I've in the past caught recruiters that have added/changed my resume to suite their requirements better, so having only a PDF actually helps stop that nonsense.

http://bertjwregeer.com/Resume-files/BertJWRegeer-Resume-Apr...

(Side note, I am looking for work, feel free to contact me!)

[themoonbus]

Oof. I know you didn't put up your resume for critique, but it is far too wordy... A resume should be something that a person can glance at to get a general idea of your career.

The interview (and to a lesser extent, cover letter) are where the specifics come out.