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.