Networking Tonight

Because it's a Networking event (Tech Tuesday), I will be refining a few things, possibly doing a business card connect dump and then grabbing a shower, putting on my glad rags and then attending.

New flow

 

So the revision part is what's going in now - a level of persistence to be reflected on, regurgitated and checked again by a human.

Persistence is good

 

I was impressed with that - so now I can set up some kind of persistence within the conversation that will disappear when I quit.  Of course, logs will exist, but wow this has some real potential going forward.

Existence is pain

Monday Stuff

 

That does seem to be the plan.  

I am currently modifying the tool to move forward with some feedback and tinkering.

That's the fun part - let's see how it looks with the individual job descriptions modified and tailored to match the tone of the job description.

Prototyping

This was a success for one attempt - it was good to see how it all worked out.

I pumped in a known job description and managed to take my existing "Summary" and it created a new one that was more fitting for the job.  Now, it's time to take that into the code of resume-builder and put that modification in.

Consent

So, the next part after getting things rolling is to ensure that the proper consent is present for publishing the cover letter, and the possibly modified Summary section.

This will take a slightly higher priority in things.  So, a previewer, checks, and then publishing. 

Refinement of things is good.

 Okay - this is working.  

 

So yes, the filtering is getting  better and the prompt magic and temperature seems to be "the thing".

It is still generating a cover letter which I'll have to cut out.

I'm not dumping out the skills gap between my CV and the job description.  That can come next after I do some silly escape-code wrangling with the .yaml file and how pdflatex works.

Overall, it does look nice and the data is accurate.

 

Progress continues.

 And the improvements keep coming along:

 

So the flow is as follows: 

• Navigate to the site;
• Enter the Company Name this is used for storage;
• Enter the Position - this too is used for storage reasons;
• Copy and paste the Job Description
• Press "Analyze & Generate Drafts"

GUI Building time.

The GUI is now needed - a web-based approach so I can access it from around the world.

The GUI is simple for now

 

It will now generate the 5 levels of verbosity.  Now to integrate that with the "fitness" of the job description.

Fitness thoughts

Right now, just testing out my ollama instance with llama3.1 and seeing if it can match fitness between an existing job description and my .yaml file resume.

Data is entered, values, dates updated...

Today was a success - the format is now in.  The template .tex file is good to go, and the renderer.py script is generating the proper output to be converted to a PDF.

It looks clean and lovely.

It is checked into git and ready to be experimented with to add the levels of verbosity.

This is key to a successful venture.

 

 

 

Next day cleanup.

The renderer.py script was missing my "education" and "personal projects" section from the resume.  I fixed that, and with some other tweaking, the resume is looking much better.

I would like to add the final layer of verbosity: 

For each skill under a task, there should be an explanation as to why it was used, and notes about the implementation.

It's a bit of overkill, but I think it's worth it for ultra-verbose resumes.

       - task1: >-
          Client 1: Developed test automation of a large robotic
          thermal/pressure industrial system.  Wrote automated
          test cases for this system.
        skills:
          - Python
          - pytest
          - uiautomate
          - Selenium
          - Equipment Interfacing
          - C/C++
 

To this: 

        - task1: >-
          Client 1: Developed test automation of a large robotic
          thermal/pressure industrial system.  Wrote automated
          test cases for this system.
        skills:
          - name: Python
            level: 8/10
            reasons:
              - existing culture
              - rich ecosystem
            challenges:
              - first time working with Python and Windows
            benefits:
              - rapid development
        ...