Daviey

Reviewing content, classifying data, making decisions.

That may be true, but in the history of NATO how many countries have invoked Article 5, and which countries answered that call?

Why do you assume that retirement = life over? If anything, now he has the opportunity to enjoy life on his terms.

How would the base model know bespoke organizational policy, process and nuances without some way of briefing it?

The recruiter wouldn't compile anything, they'd just tell me "this guy sent me a GitHub repo instead of a CV", or more likely just not mention your application. A recruiter who reliably funnels screened people to me is worth far more than any single application, so that's how it plays out logistically - you get dropped and never hear about it. "As far as I am aware" is carrying a lot of weight there.

The arrogant bit is "here's a link to the source and instructions on how to compile it, feel free to do what you need". A recruiter asking for an editable version wants something they can drop their letterhead on and forward to the client. Handing them a build task assumes they have both the skills and the inclination to meet you on your toolchain. Nobody expects you to be their typesetter either; the difference in skills isn't the problem, assuming the difference away is.

That mismatch is the part I'd actually be screening for. A company is mostly non-engineering people: sales, support, HR, PMs who can't read a diff. The recruiter is the one non-technical person in your hiring pipeline, and how you handle them is a sample of how you'd handle the fifty you'd work alongside. If the instinct is to make them come to your toolchain rather than meet them where they are, that plays out in every meeting and every "quick question" from sales for as long as you're employed. The CV is the one document whose entire purpose is to sell you to a non-technical audience, and handling that poorly is telling.

I've maintained my own CV in LaTeX for ~20 years and would never dream of sending a recruiter a Makefile and telling them to work it out.

Sent to me directly? Fine, I'd read the repo, probably be impressed, might even see if I could improve mine from it. That was never the scenario though.

If you did this to me, fine.

If you had done this to a recruiter that funnels screened people to me, I'd make sure to not interview you. It shows total lack of awareness of how to deal with non-tech people, verging on arrogance.

When I need other people to continue editing it.

I also prefer LaTeX, I've written hundreds of letters, multiple papers, a few thesis and my CV (maintained for the last ~20 years). But the defacto for business documents sadly isn't LaTeX.

The biggest blocker for me is having confidence my output renders the same with people using MS Office, pdf output isn't always sufficient.

I have 3-5 agent harnesses with large context windows working on different applications concurrently.

I paid $360 annual for Max plan and currently averaging about 1BN tokens a day with their frontier GLM-5.3 model. This was clearly unsustainable for them and they've dropped this package.

Most companies I think now make you accountable for the card, and unless you provide a receipt showing it is a company expense then you are accountable.