Live data from Hacker News

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

ktema.org

81–90 of 122 posts

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

#81

Can't we all just agree as an industry to use LinkedIn profiles and move on to more productive things? I know they're horrible but come on already.

That is too pragmatic for an industry the pretends it values efficiency.

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

#82
post #66

Earlier quoted context omitted.

I would be careful with LaTeX. I use to have a LaTeX resume generated with LuaTeX. At an old company, I saw my LaTeX resume in the ATS long after I was hired. Apparently, something happened and the PDF displayed as blurred-but-not-unreadable in the ATS. Maybe the ATS did some post-processing or used a limited PDF display engine? Lucky for me, the resume for that job was just a formality. These days, I just use Google…

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

I wouldn't worry about automated ATS. Their use is way overstated on LinkedIn, by "resume experts," etc.

I'm talking about whether a human can read the document comfortably.

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

#84

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…

My resume is in LaTeX, but I like using a nix Flake so I can easily run `nix build` to build the resume, and I've guaranteeably installed the correct version of texlive that I need cuz it's reproducible.

Nix obviously isn't strictly necessary, but making a flake wasn't terribly hard and it's nice to keep stuff standardized between distros and macos.

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

#85

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 think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility.

Learning curve is a thing: I've never touched LaTeX, and I don't anticipate using it in the future. If I wanted to automate a thing as a learning project, I probably would rule out LaTeX unless I had a reason to want to learn it.

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

#86
post #79

Earlier quoted context omitted.

That's fixed. Many thanks for taking the time to report it :)

Did you mean to spell "Product-focussed" with 2 s's?

I did. I accept that a single "s" is more common, but I like the double "s" and I don't believe it is considered wrong (yet).

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

#87
post #85

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 think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility. Learning curve is a thing: I've never touched LaTeX, and I don't anticipate using it in the future. If I wanted to automate a thing as a learning project, I probably would rule out LaTeX unless I had a reason to want to learn it.

You don't really need to know LaTeX to do a resume in LaTeX, you just need to get a template and add your data to it

source: my resume is the only thing in LaTeX I've touched in over a decade

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

#88

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…

Hi, do you have an example of your latex source or template?

Here’s a sparse copy of mine.

https://michaelwilly.com/cv/latex

I don’t want to share the git because my real resume has more details.

I learned tex during a degree, I can use it mainly for math notation but I’m not sure that I know it in and out for typesetting.

My resume now uses a template.tex and a main.tex file and I \\input sub section tex files so I can iterate using git.

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

#89

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…

Look at that subtle off white coloring. The tasteful thickness of it. Oh, my God. It even has a watermark.

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

#90

Earlier quoted context omitted.

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.

I agree that most LaTeX CVs are kind of boring. But I think they are more interesting than the end product in TFA, which I found completely underwhelming. 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…

> But I think they are more interesting than the end product in TFA, which I found completely underwhelming.

I agree, that's a quite bad CV layout wise. Like someone has said "must be no more than 2 pages!" and his solution is just to eliminate all spacing.

Post reply on HN