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

Building My Resume in HTML Using Eleventy

michaelengen.com

Post reply on HN
Print view View original

51–60 of 73 posts

Re: Building My Resume in HTML Using Eleventy

#51

Post by occamschainsaw »

ruthmarx wrote: post #10

I've been using LaTeX for mine for years and never looked back. I have it setup in such a way that I just comment or uncomment a few lins at the start and can easily include or exclude, or adjust, types of skills, work experience, length, etc. Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.

Hi, I have a latex resume/cv too and am curious about "some protections against recruiters trying to copy and paste and change things". What does that mean?

Re: Building My Resume in HTML Using Eleventy

#52

Post by andrewflnr »

adzm wrote: post #29
scardipdap wrote: post #12

Points for originality, but it does seem a little complicated. I did something like this about six months ago, but in HTML, CSS, and zsh. As a next step, try testing your output with a free ATS parser.

Do you have any links to free ATS parsers? This is an interesting angle I hadn't considered.

I have considered it, but didn't find any parsers that didn't creep me out.

Re: Building My Resume in HTML Using Eleventy

#54

Post by not_your_vase »

ruthmarx wrote: post #10

I've been using LaTeX for mine for years and never looked back. I have it setup in such a way that I just comment or uncomment a few lins at the start and can easily include or exclude, or adjust, types of skills, work experience, length, etc. Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.

Unpopular opinion: every time I see anything made with LaTeX, it makes my eyes bleed. While it might be great for editing, I find it to be a pain to read. I really wish academic papers (and everything else it is used for) would be written with a tool that generate at least a bit more readable output...

Re: Building My Resume in HTML Using Eleventy

#55

Post by cryptozeus »

michaelengen wrote: post #13
cryptozeus wrote: post #2

But why ?

Author here—Two reasons, mainly. HTML+CSS is a great layout engine, and Eleventy is a good tool for making development more pleasant. While I have a lot of experience using other tools, e.g., LaTeX, I think they're not as well suited to laying out simple documents.

You are giving me “how” and I was asking “why”. No biggie but don’t really see why

Re: Building My Resume in HTML Using Eleventy

#56

Post by ruthmarx »

occamschainsaw wrote: post #51
ruthmarx wrote: post #10

I've been using LaTeX for mine for years and never looked back. I have it setup in such a way that I just comment or uncomment a few lins at the start and can easily include or exclude, or adjust, types of skills, work experience, length, etc. Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.

Hi, I have a latex resume/cv too and am curious about "some protections against recruiters trying to copy and paste and change things". What does that mean?

Honestly I don't recall exactly because it's been so long since I set it up. I think I did something to make it hard to export/convert to doc/docx, and maybe even prevent or make it hard to copy test for certain blocks. It was just using some tracks for things you can do with the pdf format, but I don't have more information at the moment.

I'll try and dig in later and see what I actually did.

Re: Building My Resume in HTML Using Eleventy

#57

Post by onion2k »

I made an Elevnty website for my partner's business. It was a great experience. It worked well and was easy to code.

After I came back to update it 3 years later by cloning the repo and running 'npm i' I got a bunch of errors. Working through the upgrade process failed. I couldn't get it running again.

I dumped the HTML from the live site, changed that directly, and just uploaded that to S3 to host it. I don't think I'd bother with Elevnty again. It's great for making a new site, but the long term maintainability isn't there. To be fair, this is on me. I should have done more to keep it running, or pinned the dependencies, or something.

Re: Building My Resume in HTML Using Eleventy

#58

Post by oneshtein »

not_your_vase wrote: post #54
ruthmarx wrote: post #10

I've been using LaTeX for mine for years and never looked back. I have it setup in such a way that I just comment or uncomment a few lins at the start and can easily include or exclude, or adjust, types of skills, work experience, length, etc. Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.

Unpopular opinion: every time I see anything made with LaTeX, it makes my eyes bleed. While it might be great for editing, I find it to be a pain to read. I really wish academic papers (and everything else it is used for) would be written with a tool that generate at least a bit more readable output...

TeX output was optimized for printing, so it looks better on paper than on screen. (IMHO, it looks excellent on paper). Try to zoom in, for better experience, or view generated PDF on eInk display.

Re: Building My Resume in HTML Using Eleventy

#59

Post by akoboldfrying »

armanboyaci wrote: post #35
Aurornis wrote: post #21

Earlier quoted context omitted.

Mine is also in LaTeX. Every 3-5 years I get a nice reminder of the nightmare that is cobbling together a fully functional LaTeX dev environment to work on it again.

I am keeping my CV on overleaf and it is very convenient. Did you try that option?

The issue for me with LaTeX is the amount of time I spend messing around trying to get different packages to play nicely together.

Sometimes you get lucky and everything just works. If it doesn't... you google it, and pray that someone else hit the same problem and solved it, because trying to actually figure out the problem from first principles is doomed -- the language (and ecosystem) makes Perl look sane.

Post reply on HN