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…
The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
71–80 of 122 posts
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#72The 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…
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#73I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#74Earlier quoted context omitted.
I’ve actually made the switch over to Typst[0] for my app [1]. I’ve previously used a quick jinja .tex template that then just pasted things in, but LaTeX can really throw some strange errors and overall handling the files was a hassle. Typst was much easier to setup and the function-based operation meant that sending variables in was a breeze with better error handling there too. Also, I just grok the syntax a lot b…
Typist looks interesting, although I've had no issues with LaTeX so no reason to change to something more niche.
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#75I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#76I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#77I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…
I have yet to see a really good LaTeX CV. I guess it is possible but in my experience LaTeX just isn't designed for that and gives boring-looking results.
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#78I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical. The resume is modular and can be u…
I have yet to see a really good LaTeX CV. I guess it is possible but in my experience LaTeX just isn't designed for that and gives boring-looking results.
Now I have spent quite a lot of time customizing LaTeX, to the point where people have come to ask how I produced certain documents, because it surely could not be LaTeX. If you have a specific design idea in your head, LaTeX is able to achieve it if you just spend enough time RTFMing.
Re: The Overengineered Resume with Zola, JSON Resume, Weasyprint, and Nix (2023)
#79Earlier quoted context omitted.
That format is really nice! I regret to say it but I found what looks like a typo - you've got "automcomplete" where I think you mean "autocomplete". I hope this helps improve your resume.
That's fixed. Many thanks for taking the time to report it :)