Ever have one of those moments where something rogue was eating up drive space such to the point that your browser acted strange and eventually you had to close it down, not knowing that everything wasn't being cached?
That was this morning. This seems like problem.
Emails are mostly back up and running, linkedin account salvaged...
Nostalgia
The resume rebuild is going well - fixing up references, wording, and all placed into a yaml file. I expanded some new fields:
tldr:
This is a short description of my role at a company. It allows for a simple level of verbosity when generating resumes.
proudof:
This one I like - it highlights what I was proud of when working there.
overall structure
- company: "<company name>"
position: "<last job title>"
location: "<city, province>"
start_date: ""
end_date: ""
highlights:
- tldr: >-
What did I do there in an executive summary.
- proudof: >-
What did I do that I was most excited about or proud of.
- task1: >-
A bullet point of what was done while limiting skills/technologies
specifically out for another level of verbosity.
skills:
A deeper level of verbosity - specific skills/technologies used.
In particular, languages, management, protocols...
- task2: >-
...
skills:
...
I have contemplated putting another level of description for the skills. This can round out my thinking at the time, implementation problems, etc...
Time for a shower and lunch!
So what's next?
Take that yaml file and a job description and then throw those at my local LLM and do some parsing magic. Okay - there will be some playing around with the prompt so that the system believes that it's an expert technical career coach and resume writer.
Done
And, yes...
The output is a json format. Time to take that out and pass it through a Jinja2 formatter - it's a great formatter - so I can output a LaTeX file. Yes, I said LaTeX. It can be easily dumped into a pdf file for laters with pdflatex. Now is time to work on the formatter.
No comments:
Post a Comment