Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

ktema.org

Post reply on HN
Print view View original

101–110 of 122 posts

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

#101

Post by OJFord »

DEADMINCEDOS wrote: post #35

I 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…

> It's optimized for all the ATS nonsense it inevitably gets run through

How did you do/test that? I help maintain (didn't author it originally) the AwesomeCV template; we have an open issue about this, inconsistent results and not really having a good way to test it.

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

#102

Post by OJFord »

DEADMINCEDOS wrote: post #69
Ilasky wrote: post #50

Earlier 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.

You've never had an underfull hbox?

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

#103

Post by wonger_ »

tarxvf wrote: post #96
DEADMINCEDOS wrote: post #70

Earlier quoted context omitted.

I've made sure all the most commonly used ATS systems can read the produced PDF without issue.

Do you have any tips, code, or even just a list of the common ATS systems? I need to do this with my latex cv but I'm not even sure where to start.

I think this open-source parser details a typical ATS algorithm: https://www.open-resume.com/resume-parser

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

#105

Post by 1vuio0pswjnm7 »

mananaysiempre wrote: post #98
DEADMINCEDOS wrote: post #68

Earlier quoted context omitted.

There is no reason to mention it, though. It's like mentioned Ubuntu as being necessary for having made a resume.

Nix ≠ NixOS. Nix is a build tool (like make or Ninja or Bazel) with strict isolation of builds and caching of artifacts. NixOS is a distro built on top of that tool, like the BSDs are built on top of make, Gentoo on top of Portage, or gittup[1] on top of tup. Running NixOS while you’re building your resume is irrelevant; using Nix to create the final artifacts is a material statement about the chosen toolset. [1] htt…

BSDs use ports or pkgrsrc which are "built on top of" make

Gentoo uses portage which is "built on top of" python

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

#107

Post by felipeerias »

IshKebab wrote: post #75
DEADMINCEDOS wrote: post #35

I 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.

A CV created with plain boring LaTeX is perfect for the right audience: people who can identify a LaTeX document at first sight.

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

#108

Post by tneely »

DEADMINCEDOS wrote: post #35

I 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 took a similar approach with LaTeX, where I have a GitHub workflow [0] that regenerates my resume on commit.

[0] https://github.com/tneely/resume/blob/main/.github/workflows...

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

#109

Post by deepspace »

taeric wrote: post #76
DEADMINCEDOS wrote: post #35

I 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…

LaTeX is fine to me, as well. Heck, now that I'm older, I think bare TeX is probably fine. In line with what you are saying, I can offload the semantic nature of my resume to text files and just use the markup of TeX to layout how I want the page to look. Much easier if I don't try and have a single source that is both all of my semantic data with the layout at the same time.

I store the customizable data in YAML format and then use mako templates + a python script to transform my custom resume- and cover letter data into Latex | HTML | Plain text

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

#110

Post by deepspace »

lelanthran wrote: post #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…

The bullets to the left of the titles make my eyes bleed.
Post reply on HN