I found that continuously updating my CV over time was a pain, so I simplified it and automated it. These days I use a simple CI workflow in a GitHub repository that generates a new .pdf CV based on a Markdown source file. If you like the sound of this, I’ve created a GitHub template for this pattern, should you wish to follow my example. The template contains placeholders to fit the structure I personally use these days, and is littered with tips and advice for how to write a good CV (I say this as someone who’s screened a lot of low-quality CVs).

Keeping your code’s dependencies up to date is hard, so luckily there are free tools like Dependabot around, that can create PRs against your repository whenever any of your dependencies have a more recent version updated. Depending on the size of your codebase, this can turn into quite a chore as you have to verify that the dependencies don’t break your code. A common solution is to establish a thorough test suite and other CI checks that you trust to let you know if your code is broken and combine that with automatically merging Dependabot PRs.