I’ll be quick, this is just an update to my last post!

In my last post, I wrote about how I made dzil workflower to install GitHub Actions into my Dist::Zilla-based dists’ repositories for automated testing. I also said I’d been reading O’Reilly’s Learning GitHub Actions. This week, I applied some more of what I learned from the book, and it was good.

Starting ages ago, once in a while somebody would show up and offer me a commit that would add some automated testing system to my open source repositories. I liked the idea, but it always felt like a free puppy. I didn’t know how it worked, I didn’t know how the YAML file (always YAML!) was put together, and I didn’t know what I was supposed to do when something went wrong.

Every time I store an API token in a plaintext file or an environment variable, it creates a lingering annoyance that follows me around whenever I go. Every year or two, another one of these lands on the pile. I am finally working on purging them all. I’m doing it with the 1Password CLI, and so far so good.

Years ago, I found an iOS app called World Uncovered. I used it for a while, then forgot about it, then started using it again. It’s pretty cool, and I keep telling people about it, so I thought I’d write a post about it.

One of the things I wrote at the first PTS (back when it was called the Perl QA Hackathon) was Module::Faker. I wrote about it back then (way back in 2008), and again eleven years later. It’s a library that, given a description of a (pretend) CPAN distribution, produces that distribution as an actual file on disk with all the files the dist should have.

Almost exactly a year since the last Perl Toolchain Summit, it was time for the next one, this time in Lisbon. Last year, I wrote:

A couple years ago, I posted about making a Prometheus exporter for my Chrome tab count. I had fun doing it, but unfortunately it made it onto Hacker News, which as always got a fair bit of missing-the-point. So it goes.

Almost a year ago, I started reading Fluent Python. I finished it yesterday, and I have to say, it was great. With a few big breaks for various uninteresting reasons, I read a chapter or two each weekend. It’s one of the best technical books I’ve read in years, and I think it’s going to significantly improve my use of Python.

For a few months now, I’ve been putting off reading any of the management and leadership related books in my queue. For whatever reason, my internal gears recently turned enough that I felt like picking one up. Probably it’s because I spent a week in Vienna. I should write about that, too. Anyway, I picked up one of the books on my list and read it, and that book was Meeting Design by Kevin M. Hoffman.