Live data from Hacker News

The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

ktema.org

11–20 of 122 posts

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#11
I have a resume in latex, all I have to do is change a couple lines every now and then and run the default latex pipeline, all of it directly from gitlab. It worked on the first time I tried and every time since then, it produces a pdf which I can then download and send.

I noticed the container they run uses nix too, which is nice although I don't care about it as long as it works. I could add signing of the pdf maybe some day for fun. What's great with this approach is how little hassle there is and nothing to install, nowhere, and produces the same clean resume I've used for over a decade (but needed to install a thousand things I could never remember from one computer to another).

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#12
The linked resume is a poor example of the process.

It's neither visually pleasing nor is it more easily readable than other CVs that I have seen.

It's fine for a CV to be visually ugly as long as its readable, or visually attractive in spite of being less readable. You can't fail at both dimensions.

If you're really happy with a CV that looks and reads like this, save yourself all the effort and make a RTF document instead.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#13
I wish there was a standard format for resume that was universally used. Every HR website requires you to upload a resume to apply, then tries to extract the various experiences and details automatically, invariably fucks it up completely, and you end up having to spend 20 minutes to correct it manually. Unless they treat this exercise as a form of captcha…

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#14
Automating your resume is a bit of a rite of passage for new software engineers. It just feels like a stupid repetitive task.

I've found that I change job summaries so often, that automating it was a net negative in time spent on the thing. So now I just do the same as the digitally challenged: copy a Word file to "resume (DATE).docx" and change the contents as needed.

My younger self would be surprised, and slightly annoyed, at how often I use the "dumb" solutions for problems.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#15
I did something similar but with my phone, the android orgzly app, termux, jinja2 and latex.

I cribbed a CV template from overleaf and put some jinja2 in it to take the content from CV note in my note taking app: https://hitchdev.com/orji/using/latex-cv/

With termux I can then hit a button to run a script and it will instantly generate a pretty PDF using latex from an orgzly note and fire off an android share intent.

The nice thing about this set up was that if a recruiter called me while I was out and wanted a CV quickly with a couple of tweaks made I could just do it on my note taking app and email an updated PDF in a few seconds.

In theory I could easily change the style of the CV but in practice I haven't felt the need to touch it in years.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#16
I also over-engineered how I generate my CV[1], but went the opposite direction by using Dhall to create JSON and LaTeX files that I use to create a PDF and GraphQL API in Rust for it, automatically deployed via CI/CD to a VPS and a tagged GitHub release. It was a lot of fun to make, but is so over-engineered I hardly want to touch it anymore :)

[1]: https://github.com/sondr3/cv-aas

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#17
It is definitely overengineered and, unfortunately, outdated, as the most recent position in the resume and about page do not match. A lot of effort for something that is not accurate and obviously not used to apply for jobs, which is the purpose of a resume in most cases.

A simple file (Word doc, Numbers, Google Doc) that receives a change every few years and is exported as a PDF seems to do the task better.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#18
post #13

I wish there was a standard format for resume that was universally used. Every HR website requires you to upload a resume to apply, then tries to extract the various experiences and details automatically, invariably fucks it up completely, and you end up having to spend 20 minutes to correct it manually. Unless they treat this exercise as a form of captcha…

In Brazil we have Lattes (https://pt.wikipedia.org/wiki/Plataforma_Lattes). The English translation does not mention it, but one of it's most useful features is a centralized resume platform. It's quite nice, but mostly used by people in academia and government-adjacent areas.

Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)

#19
post #13

I wish there was a standard format for resume that was universally used. Every HR website requires you to upload a resume to apply, then tries to extract the various experiences and details automatically, invariably fucks it up completely, and you end up having to spend 20 minutes to correct it manually. Unless they treat this exercise as a form of captcha…

EU has the Europass, I just use that.
Post reply on HN