[bennylope]

> As others have said, I don't really get the fascination with LaTeX.

I have gone down this path with other types of documents (reports, proposals) not because I love LaTeX but because I hate composing and editing in Word, etc. Especially for long lived or repeated documents. Some of those tech clients might just prefer working with plain text for editing, source control, and/or version branching.

[kemiller2002]

You've never really "lived" until you realize that your document with the different sections, etc. that you've painstakingly setup is broken because of a copy paste issue when adding a new section. LaTex maybe a pain, but at least the output is consistent. There is no magic where the formatting bleeds over due to something you can't see on screen.

[thrwyoilarticle]

Underfull \hbox (badness 10000)?

[im3w1l]

The odt format is xml in a zip and simple enough that you can hand edit it if you really want to.

[dhosek]

I used to do my resume in a custom TeX format.¹ It looked gorgeous. But because so much of tech world hiring is mediated by recruiters and automated resume ingestion systems, having a straightforward document in Word ended up serving me much better.

1. An ancient resume macro (and an ancient resume) that I made while a freshman in college is on CTAN. What I used in my early career was not that, although I doubt I have any relic of that later file anymore.

[cookieswumchorr]

I never had the time/brains to get past the learn curve with LaTeX. Recently I started using a pipeline of markdown to html with Pandoc and then to pdf with Dompdf for project documentation.

Turns out you get neatly formatted printable docs with not so much effort, and the raw markdown stays with the code where it can be used and updated by fellow devs

[jjjbokma]

Fwiw, I have made a LaTeX resume template [1] for Pandoc. Input is markdown and output is LaTeX or LaTeX rendered to PDF.

[1] https://github.com/john-bokma/resume-pandoc