Hacker News new | past | comments | ask | show | jobs | submit login

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.




Except that it is a great learning experience.

Data driven resume was my introduction to LaTeX and I had a great time building it.


LaTeX itself is sort of a rite of passage. It's slightly more useful, because the mathematical side of academia runs on it.

There's a bunch of template you get for free by doing what everybody else is doing. The corporate world has those too, but for Word, because that's what they use.

There's this subconscious believe that something that has a steep learning curve will make things easier later on. That is not always true. If you want stuff that is more complex than normal, Word and LaTeX are about equally as annoying, if nobody solved it for you (templates, Google). LaTeX is just harder for the easy stuff too.

Doing my resume was the last thing I did in LaTeX, not the first. Doing anything in LaTeX just stopped being useful when the recipients didn't recognize Computer Modern anymore.


Yea, no need of over-engineering.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: