Fair. Btw you can get some functionality out of this without LLMs:

Job discovery with automated filtering doesn’t use LLMs. Then, you can pass the screening without an LLM step (just pass “H” instead of “L” on the prompt to make a human screening). Then you reach tailoring of a CV to a job posting, which is the first hard need of LLM, but you could stop by that point, or even fork to skip to the tracking step, which again has no LLM.

The general issue is that without LLMs, this project is a somewhat basic pipeline/scraping/knowledge-base approach to job hunting, and you can likely do it yourself with a bit of python scripts and vim. My idea was to use LLMs to explore how far this space can be automated more holistically, in a reasonable way.

Honestly I was a bit shocked with how vibecoded other projects on this space are, so I wanted to see how a non-vibecoded use of LLMs for job search would work.

I’ll take it. You’re probably thinking of embeddings or some other non-LLM AI approach. I guess my point is that the current economic availability of LLMs and lack of experience and time to explore cheaper alternatives is why this project landed how it did currently.

Right after that quoted sentence, it says “this project uses as little LLM as possible.” I stand by that, as I cut as much LLM as I was able.

Typst is cool. I probably would have used it myself if it were mature enough by the time I started with this project.

I would also point out that users of roffume can consider roff an “implementation detail” and ignore it entirely. The main benefit of roffume is the creation of “per-application, self-contained folders” containing all inputs (markdown), outputs (PDFs), and commands.

Good point about style; I was thinking more about \f[I] than .I. So yeah, I see that if you have every semantic thing on its own line, diffing and maybe readability is better.

Makes sense, thanks for the reply. You have a point about “diff by line”, and I might have not gone all in on serious roff to land on all the benefits.

Another thing I see as an example of markdown being slightly more readable: Unlike roff, not needing to escape some typographical marks (like - to get a hyphen). And the better syntax highlighting support for stuff like bold, italics, and so on in Markdown.

deleted by creator

Good question. I had an unreleased version of this project running on groff only for quite some time.

After using it for 25 or so applications, I got the feeling that having markdown as the “source of truth” was slightly easier for reading, checking, and diffing different versions. I’ve been using it with Markdown as a base and I’m happy with the results.

Basically, I found Groff’s syntax slightly “heavier” than Markdown for everyday visual use.

Having said that, I know that a lot of the visual clutter issues can be fixed on the groff side. If you actually have a groff resume format that is very readable for you, I would like to take a look and maybe reevaluate if i’m doing groff the right way.

Thanks for the feedback. I’m the author of the medium blog post too.

If you have any tips on where to find a better free voice, I’m all ears. I haven’t tried chatterbox yet, that one might do it.

It could also be that the “direct blog post to video” format doesn’t cut it. But I’m still experimenting with ways to generate effective multimedia out of my content.

Btw, this is my open-source pipeline, which I use to make the video and blog post out of the same source file: https://github.com/sebastiancarlos/hacker-press

Edit: Regarding “satire”, that doesn’t apply to this blog post in particular. But I did add some jokes here and there to keep the dry topic going.

Well you know, someone has to write the great software novel of our time. If no one else was gonna do it, i had to give it a try

Lol, you know the lore

Someone has to reclaim them for mankind

Due to hug of death, backup is accessible here: https://sebastiancarlos.github.io/hacker-fables

Salvador Dali - Corpus Hypercubus

Yes! That’s exactly the inspiration.

Thanks!

I was actually wondering if this could be packaged. At least AUR should be doable.

Great question! Yes, Backbone appears twice.

First, it’s artistic license. I think the Backbone.js school is the “backbone” of our current front-end era, for better or worse. So, it fits that the backbone of the hyper-cubical cross is represented by Backbone.js (twice). Spoiler alert: The cover art’s meaning becomes clear around the halfway point on the book, if you’re curious.

Second: Yeah, that was a “happy accident” by genAI. To be fair the first $50 that gets donated for this book on my Kofi link go directly to commission a real artist for a cover remake.

That’s “Backbone” (https://en.wikipedia.org/wiki/Backbone.js)

It was the hot front-end framework before Angular (and React).

glad it landed, thanks for checking it out