Got the first vaccine shot for Kiddo this morning, and resisted, just barely, the impulse to high-five every dang parent in the pharmacy waiting area.
Spent a good chunk of today alternating between Forza Horizon 5 and learning how to add a vim layer to my keyboard with QMK. Pretty good Saturday tbh.
Oh, this keyboard hobby is going to be a Thing, I can tell. I got some alternative switches to try in my Q1. These are quiet tactile switches, slightly stiffer than the stock Gateron browns. I swapped them in for ESC and return, and got a nice, just stronger feel with less ping.
With my iPhone constantly remind me that it’s just about out of storage space, I realize that I never got around to turning on iCloud Photo Library. I’m not sure why, but I probably had some logic. These days, is there any reason not to turn it on?
Destiny 2 Power leveling tool in R
The latest piece of my homebrew Destiny 2 toolset is Travelr, a power leveling tracking tool built with R and using a much simpler process than most of my prior nonsense. (Aside: I'm still using ArmoreR, but it has some key limitations that I haven't spent much time with, including a problem incorporating the authentication flow more fully into Shiny so that I could make it an app that others could use in a more friction-free way.)
The power climb is part of the game with each new Destiny season. A lot of this process is luck: A player can only get so many pinnacle drops per week and there's no guarantee that a given drop won't be in a duplicate category. But, some drops can be targeted to broad categories -- armor versus a weapon, for example -- and there is some efficiency across characters if you can strategically raise one category to increase the base level for all characters.
I was inspired by a fantastic tool written by a member of the small Destiny 2 community I'm in, that identifies categories to target (or, try to target, anyway; a lot of it is still frustrating random luck, sometimes), and decided to try building my own version. It doesn't do anything unique, but it works and it's wonderfully satisfying to step through an R markdown notebook that authorizes me to the D2 API, retrieves all my equipment statistics, calculates my maximum power level and indicates which, if any, categories should be targeted.
For example, here's a screenshot from the beginning of the season, where every single equipment type would increase my total maximum power level:
... and later in the season:
It's been great fun to have this small tool with me during the season's play. It's currently dependent on another small tool that grabs the equipment "manifest" file, and I'll be publishing the whole notebook to github when I finish incorporating that into the repository.