Clojurians Log v2

I did mine based on a yaml file that I parse into HTML, then print to a PDF. I also used babashka tasks to orchestrate the whole thing. I used yaml instead of markdown simply because I figured having a bit of structure would be useful when manipulating the file to produce custom CVs for each role I applied to.

I've seen folks make their resume in HTML + CSS, and then you can use @page and @margin to set how it prints to PDF

https://typst.app/ (https://github.com/typst/typst) is pretty great!

https://typst.app/universe/

some nice resume templates in there

I have a latex file for my resume, which is the only place I use latex these days, and I have a makefile to build it, but it uses the bsd make dialect because I was using freebsd 15+ years ago when I first wrote it. So I keep having to install bmake (the typical name for the bad make package on Linux) and re-learn latex every 5 years or so when I need to get another job. Which is to say, what's wrong with Word? (I briefly thought about moving to typst, but bmake isn't that hard to install)

Me becoming insane is about me being nowadays very comfortable with other ways of manipulating text and not used anymore to use Word (or similar), but I don't think there's anything wrong with it.

I made my resume in google docs, it was fine and people seem to like if

I do wish I had CSS-like style control

Yeah, raw html seems super appealing. Lots of control, you won't have to worry about keeping a build environment around for it

and backwards compatibility is stellar

I think your resume needs a PDF format. Recruiters work in their ATS system and will just pull up your resume quickly there. If the HTML resume makes a nice enough PDF (as Cora suggests), then no worry there I guess. A colleague gave me his LaTeX template. It was gorgeous. When I really needed to hone it down to one page though, I didn't get around to learning LaTeX enough to tweak it the right ways. For the time being my new (one pager) resume just lives as a Google Doc. Now I want to try Typst though. It seems like that or TeX shouldn't be too much work.

I use markdown with a little inline html and a custom css file. I use pandoc to render it to html and “print” it to pdf from my browser. I can share my code with you if you like. I used to use other markdown renderers but I’ve found that most software in that space changes too quickly for something I only touch once every few years. . Pandoc is rock solid, installable via system package managers, and has a Clojure-like approach to backwards compatibility

I'm using a LaTeX template I found online, twiddled with it a bit, it looks nice

When I was looking for new jobs I've created a repo in which you can write an edn file and run a command to produce the pdf. Here it is in case someone is interested https://github.com/danielhvs/nerdCV

I used an orgmode based solution, which works really well for me.

Here is the repo, an incredible idea: https://github.com/kishvanchee/orgmode-resume

@mario.giampietri since you mentioned Emacs, I think you definitely need to give it a try, and I just found out there are other similar ones on GitHub.

Thank you all for your suggestions 🙂

Raw HTML for me too, with all CSS and images (icons, really) embedded, making it an all-in-one, single file, plain text, version controlled document. It has some custom CSS for print media, but I'm not sure if it has ever been used. I serve it from my personal site, allowing me to monitor access to it. If a job application requires a PDF, I create a bespoke "please find my hand crafted CV [here]" PDF (HTML printed to PDF). If that's a problem (it hasn't been, so far), the company probably won't be a good fit for me anyway.

Taking the HTTP access monitoring a step further, someone I interviewed recently added an interesting twist: application specific basic HTTP authentication credentials. So he would generate and attach evilcorp:letmein credentials to an application to E-corp. This gives even more info in the logs as to who is accessing your CV.

https://github.com/yogthos/resume is interesting to me. I think my resume was in an online latex site (sharelatex or something, maybe overleaf) and i think it is gone now

ha! still there

‼️ I'm really intrigued by the idea of imposing to anyone who wants to read my CV the installation a tool of my choice and having them running npm i (or equivalent) 🤣

that would be incredibly strong signal. Not sure which way it would cut though

are you that in demand that that would be a useful filter for you?

because damn, that's impressive if that's the case

> are you that in demand no, but still I enjoy the idea itself 😁

I presume the Yogthos repo above is to build their own CV but the first instinct was reading it as wanna read it? Go npm i it yourself

the only people i would build a resume for are the people i wouldn’t need to see a resume for 🙂

I read that as "go npm i yourself" which is a lot more funny

I mean, a PDF is a PostScript program, everyone just already has an environment to run it

there was a beautiful exploit where someone made a vm in a pdf. i forgot the details

https://github.com/doom-pdf/

https://pdf-insecurity.org/pdf-dangerous-paths/attacks.html PDFs are wild

I have a LaTeX resume that I edit/produce-PDF directly in Texmaker: https://www.xm1math.net/texmaker/