5 reasons why Git based resume is awesome

The author keeps a resume on GitHub instead of using a normal document workflow. He says this fits how he already works with Git, helps with backup, and makes the resume easy to edit, share, and maintain across devices.

Reading notes

#

• The resume is stored on GitHub and updated there, with Git used for version control and backup.
• Portability lets the author show and edit the resume from different computers, including someone else’s PC.
• A friend can review the repository, correct mistakes, and send a pull request, which the author merges after checking the diff.
• CSS knowledge makes layout changes easier, while tools like Sketch are mentioned as less suitable for writing the resume itself.
• Git reduces confusion about which file is the latest version, since Word-style filenames can multiply and become hard to trust.
• The author prefers any text editor and avoids MS Word’s interface and multi-click export flow.
• HTML, webpack, Chromium headless, or wkhtmltopdf can be used to build a PDF, and the build command can be added to an NPM script.
• The author wants to add CI, I18n for English and Japanese, and eventually a web page for the resume.