Jul 05, 2026: sun day, fun day

After I published yesterday's chronicle, I also attacked another lingering problem with my environment......code coverage. I used to have a drive to incorporate CI/CD, testing suites, and any number of other modern coding practices into my workflow here. Right up until I was spending more time cleaning up the tests than writing.

Writing code or writing, writing. I'm really here for the writing. I remain compelled to write.

Good news on both fronts: at [redacted], we are firing up our first repo on the corporate GitHub site this week and that means we'll be playing with code at work! When I say we, I don't really mean me, cuz here I am on vacation. Instead, I've given one of my main partners all the tools they will need to get this going while I'm away. We call him, the wolf (true story). From there, he and I will collaborate to bring this new codebase and overall approach to the broader team. To include all the bells and whistles I learned about here months and months ago.

I wasn't supposed to be working today, but it looks like I've got some takes to get off my sweaty chest (Orlando is actively cooking me rn). 9 months in and I've got my hands on a burgeoning development team, and I will be interviewing an ERP manager upon my return to the office next week. Not exactly right where I left off on my original career path - mostly because it's better. Much, much better.

As for the other front with good news: I have to write a lot at work. My entire team is remote, we are supporting dozens of locations across the nation, and I enjoy moving hundreds of folks (either directly or indirectly) along a journey - largely through the written word. Oh, I chirp a lot, don't get me wrong. My best work though? Word salad.

Here is practice for there.

Point being, the bot improved my code coverage last night. This should eliminate an annoying reminder that not enough of my code is being tested - another we'll see when we deploy to prod situation though, stay tuned.