Post Thanksgiving Blues

And so the day starts again, clean slate w.r.t. git, test cases, and now time to mess with things to bring a simple stand alone Flask application into doing more things.

  

Renderer

Renderer needs to be put in a class so not only can it be easily tested, but also more manageable for the future.

It is comprised of some standalone functions to deal with cleaning ampersands from the text, and a huge monolithic function called: build_resume.

It really should be renamed as render_resume. 

Moved it into a class now and writing up additional test cases for going forward as I develop it.

Coverage

 

Enhanced coverage so I'm reasonably happy with the progress - the test did manage to push things further along with a flaw in the design.

 

 

 

Success!

All tests are passing, code is cleaned up!

 

The basic functionality does seem to be working despite some bodged together code.  The verbosity does seem to be working properly and the output is in the jobs/<company-name> folder.

The modified .yml file is not being populated but left as a stub for now. 

More Test Cases for Ba'al!

The refactoring is slow right now - seriously I need more test cases in place before I do the next stage.

This way, if I make a mistake, I'll know it first hand.

I just found one bug that needs to be fixed for making the code testable.  Yay.

Almost through the flow

Just have to explore the cases of accepting/denying and checking if that logic works or not for pass/fail cases.

Then.  And only then, can the next round of functional improvements can begin.

It's all good.

 

Yikes!  Failures!  But to be honest, this is a good thing.  When testing, failures means that something needs to be fixed.

Instead of just letting a system die, it's time to fix things.  Otherwise, it's just giving up or what we used to call: Windows 3.0.

Yes, there is a reference to Tidy Bowl.  Product Function: It uses blue or lavender liquids and tablets placed inside the toilet tank to fight hard water stains, mineral buildup, and ring formation between regular scrubbings.  It was also marketed as Ty-D-Bol (sounds like the topic for a podcast).

I use it as my example of a job that I would not be good at:

Company: TidyBowl (avoids messy trademarking stuff)

Role: Taste Tester

Job Description: Must have excellent taste testing skills.   A sommelier for boxed wine.

This job, like boxed wines does not pair well with my skills, typically earning a 0 score, and None for a created cover letter.  A zero score should also invalidate the button to produce output.  The only option is to return to the system.

The 3 errors were introduced with some changes to the selenium (automated UI) tests.  The fourth is a dangling error from earlier that is proving to be annoying to fix at this time.

Much better

 

The fix was simple: a breakpoint() call while I was debugging the verbosity field coming back in the request.form.  Done and dusted - back to coding the flow tests and the actual flow code.

Pieces are coming together

The pieces are coming together.  Yay!

Refactor day

Okay - first before refactoring happens, more test cases need to be written.  The existing behaviour of the system should not change.  It should just run like usual.  Old tests should pass, new ones will most likely fail, and if old ones fail, I need to jump on that right away.

Minor crisis

gitea didn't survive the crash of my system and I had to register a new user.  This also means that my jenkins install is probably borked too.  For now, focus on the resume-builder and then later, recovery of jenkins.

Oh, and the suggestions from gemini was awful.  Sigh.  So I had to reinstall as the new user and then do the old git remote set-url origin http://localhost:3001... again and then git push -u origin main.

It sucks but we dust ourselves off and try to triage what went wrong and how to prevent this from happening again after doing up the meat and potatoes.

  

 Progress

gitea is up and running - checked in changes.  Good.

Refactored the  processing and analysis code into a class and a separate file for all that is good and happy in the universe.

Test cases are working - creating a bit more infrastructure around the test cases with some canned data for scenarios.  All job descriptions, etc... are but into a testing_data.yml file for reading in and then operating.

For example, one job description that does not match my skills is for a TasteTester at TidyBowl.  I should score a 0 with the analyzer on that one for sure.  I should also not have a cover letter produced by the LLM, and no skills gap.  There's no point in extra work when there isn't one needed. 

Now I can test the ResumeBuilder class in isolation.  Once this is under control, then some more test cases need to be written up to spark up the Flask application and then use selenium to test out the UI.  I like the UI as it is right now.  Might as well have concrete tests for it as I forge forward with the remainder of the functionality.

 

 

 

 

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.