Building your resume

And when I say "building your resume" I literally mean creating a build system for a resume with config files, LaTeX and Rake. Why in the name of Knuth would I do such a thing?

1. Because it is AWESOME!?!
2. Version control! So how old will I be when my resume reaches 1.0?
3. Hosting on GitHub means my resume has an RSS feed!
   
4. LaTeX's Inline comments make for fun Easter eggs and color commentary.
5. A really keen potential employer could 'watch' my resume via GitHub. Heck they could even fork my resume and add things they would like to see me learn.
6. I could add a Rake task to publish my resume somewhere or to email it directly or even to tweet me whenever someone builds my resume.
7. Rake task for spellcheck.
   
8. I could have build parameters for adding or hiding certain sections of my resume... for example swapping out the objective at compile time.
   
9. They say "blogs are the new resumes" but I say, "GitHub is the new resume!"