Why manage your CV with version control?
Most CV builders are black boxes. Your data is stored in a database you don't control, and the history of your changes is either non-existent or is difficult to access. If you want to see what your CV looked like two years ago, or what specific changes you made last month, you're out of luck.
For developers, this is frustrating. We use version control for everything else because it gives us safety, accountability, and flexibility. Why should our CV be hosted any differently?
txtcv: Plain text CVs under version control
txtcv is built around the idea that your CV should be treated like any other piece of important code. By using the JSON Resume standard and storing your CV in a Git repository, you unlock a powerful, developer-centric workflow.
Key benefits:
- Full History and Audit Trail: You're already familiar with
git. Usegit logandgit diffto see exactly how your experience has evolved. Never lose a well-crafted bullet point again. - Branching for Tailored CVs: Applying for a Frontend role? Create a copy. Switching to Backend? Make another copy. Put them all under the same git repository so you can track job applications and CVs easily.
- No Vendor Lock-in: Your CV is a standard JSON file in plain text. If you ever decide to stop using txtcv, you still have your data in a portable and standardized format.
- Seamless Integration: Since your CV is in Git, it naturally fits into your existing backup and automation routines.