wtf is resume?

This repository is Kuber Mehta's personal resume, stored and managed using Git version control. Instead of keeping a resume as a standalone document that gets emailed around or uploaded to job sites, this approach treats the resume like a software project. Every time Kuber updates it, the change is saved with a timestamp and description, creating a full history of revisions that anyone can review. The resume itself is written in TeX, a typesetting system commonly used for documents that need precise formatting. The practical benefit is that the latest version is always available through a public website at resume.kuber.studio. This is powered by GitHub Pages, which automatically takes whatever is in the repository and publishes it to the web. There is no manual upload step, when a change is pushed to the repo, the website reflects it. This setup solves a common problem: resumes tend to fragment into multiple copies across email attachments, cloud drives, and job platforms, and it becomes unclear which version is current. By keeping a single source of truth in one place, Kuber ensures that anyone who visits the link always sees the most up-to-date version without needing to request it or wonder if they have the right file. The approach would appeal to anyone who wants to share their professional background through a link that never goes stale, whether that means sending it to recruiters, including it in email signatures, or listing it on social profiles. It also provides a lightweight audit trail, since the version history shows when and how the resume changed over time, which can be useful for tracking career progression. The project is straightforward and personal rather than a tool others would adopt directly, but the pattern itself, using version control plus automated web publishing to manage an important document, is one that founders, job seekers, or freelancers could replicate for their own use without much technical overhead.