Re:Pandoc
by throwaway81523 on Friday February 02, 2024 @02:06PM
(#39232796)
TeX documents have a distinctive look because of their typography. Back when printed resumes were a thing, whenever I saw one done in TeX, I would recognize the CM font right away. I'd then look at the resume early, since I knew that it came from a nerd. Mine was of course also done that way.
Unless you’re looking for Haskell nerds, in which case you should prioritize Comic Sans.
Re:Pandoc
by throwaway81523 on Friday February 02, 2024 @03:59PM
(#39234311)
There is also Coq's documentation system, which has its own distinctive look:
https://softwarefoundations.cis.upenn.edu/lf-current/Basics....
Simon PJ glares :)
For those not in the know, Simon Peyton Jones is one of the originators of Haskell, and sort-of-but-not-quite BDFL of Haskell... and he uses Comic Sans for all his presentations because it filters out people who will complain about font choice for a presentation.
I write code in Comic Sans, so I'm not one to judge :)
It's ideal for hiring - you immediately know which resumes to read and which one to dump into the trash.
Re:Pandoc
by throwaway81523 on Friday February 02, 2024 @09:15PM
(#39237007)
I wouldn't dump a non-TeX one in the trash. It's just that a TeX one tends to draw my interest right away.
So CVs from folks who know LaTeX good enough to change Computer Modern to something else will be dumped into the trash…
Re:Pandoc
by sam_bristow on Friday February 02, 2024 @05:21PM
(#39235237)
My personal sweet-spot for writing technical documents these days is Asciidoctor with semantic line breaks [1]. There are some warts in the asciidoc syntax but it covers a lot more of the features I need for the types of documents I'm writing compared to Markdown.
[1] https://rhodesmill.org/brandon/2012/one-sentence-per-line/
Personally I find LaTeX misses the mark. Too much markup is needed and it detracts. I'm a fan of asciidoc though. I just wish the templating was a little better though.