[tikhonj]

Not only does LaTeX make your resume look better, it also makes it easier to manage. I have a whole bunch of sections for things like different projects, experience, awards, education and so on. I can easily switch any of them out in any particular resume I want to print because they're all in separate files. The actual resume itself is just a bunch of includes, which means I can easily have multiple different permutations that are kept in sync whenever I update the appropriate sections.

Of course, this hasn't helped me at all because I haven't updated my resume in a year and a half. This might not seem too bad, but I was actually in the middle of freshman year last time I touched it :P.

[jedberg]

Yeah, that is another advantage. I use a combo of commenting things out and storing all the changes in git, so I can easily pull back old stuff if I need to for some reason.

Git and LaTex play nicely together.

[anusinha]

Heh, when I TeX-ified my resume, I used your code as a template. Just thought you might like the kudos :)

[jedberg]

That's why I published the source. Because it took me hours to find all the docs for all the different parts and put it all together. I figured I could help others out. I'm glad I was right!

[pjscott]

Oddly enough, your resume's source code is probably a more effective resume than any output it could possibly generate.

[tikhonj]

Haha, you assume my code follows good TeX style and conventions. If the only code sample I ever saw by myself was that, even I wouldn't hire myself. (That was a confusing sentence to write :P.)

If you can imagine a site with IE-specific code and a layout that's half specified with absolute positioning and half with  , you wouldn't be that far off from what my resume code looks like. It's essentially held together with metaphorical duct tape and \vspace{}.

It's like sausage--tastes great, but never visit a sausage factory :).

[jedberg]

Quite possibly. Certainly doesn't hurt!