That Microsoft OneDrive still insists on sending me photo memory e-mails, despite the fact I’ve unsubscribed a dozen times, and even though literally every picture in my OneDrive is a screenshot from my gaming PC will never not be hilarious to me.

Perhaps this is partly because the Japanese Internet continues to be needlessly opaque (it has now been zero days since I encountered a UI built around HTML image maps), but ChatGPT has become an indispensable planning partner whenever Google would normally let me down. In the case above, I just typed "search for Indigo La End concerts in Japan this June", and it got me back only the June dates of a tour I didn't know was going on, and for which tickets only went on sale two days ago. From there it was literally two more clicks to be where I needed to be in order to buy a paper ticket I could pick up at any 7-Eleven nationwide.

These days, whenever a traditional Google-oriented search workflow would have been particularly fraught—whether that's due to out-of-date information (past concerts) or SEO spam (ticket resellers)—the fact that ChatGPT will jump through two or three extra hoops for me has made a huge difference in whether I find the answer I'm looking for or get lost in a forest of tabs and give up.

Every time I sin, another device appears on my desk.

Vertical monitors for folks working on documents have been a thing for decades — now that Apple Vision Pro supports an 8K-ish ultra wide screen orientation for Mac Virtual Display, I’d love to see custom aspect ratios that allow you to create only as big of a Mac window as you need.

Why freak out about tariffs and the economy when random signs on the side of the highways in Florida are able to offer such amazing investment returns?

Last year at Rails World, I indulged in some horn tooting and victory-lap taking when I showed off the publishing platform and strength-training app I built to support Becky's business.

The paper-thin pretense of my talk was, "wow, look at how incredible Ruby on Rails is for empowering developers—even solo acts—to build ambitious products." And don't get me wrong, that was the main thesis. But the presentation was also an opportunity to show off my work and drop the mic.

As a consultant, I spent my entire career hearing how hard it is to build a real product. That as a Johnny-come-lately contractor, I could never know why things had to be slow. Or complicated. Or buggy. I lost track of how many times someone referenced Steve Jobs' epic judgment of consultants as the reason they wouldn't hire me on a contract basis and why I was only valuable if I joined their corporate family in W-2 matrimony.

Well, all that consultant FUD turned out to be bullshit. Simply by doing all the things I'd been telling others to do for two decades, I enjoyed the smoothest software development experience I've ever witnessed at any company of any scale. Literally everything went great. The resulting app looks, performs, and functions better than I ever imagined it would. My product owner / wife is thrilled with it. In its first 4 months on the market, only two bugs have been reported by customers and both were fixed in an hour or less.

Of course, one reason I held back on celebrating the success of my own ability to somehow form all the right opinions about good software was because it would have been premature. The true test of any software system is how easy it is to change later. Well, as you might be able to tell from the braggadocious tone of this post, I finally have an answer after delivering the platform's first major post-launch feature.

Becky has been wanting to start a podcast for a while, and given that we already had a bespoke CMS with her name on it lying around, it only made sense to try my hand at slotting in a podcast hosting component. I was nervous it'd take a while to get up to speed, as I hadn't touched the codebase in months. Nope: everything went so smoothly I can't believe I'm done already. the whole podcast system was finished in under 8 hours with plenty of time leftover to dunk on corporate America and the dysfunctional way seemingly every company on earth is intent on writing software.

Anyway, I've maintained a pretty meek stance over the years when it comes to dishing out categorical advice on how to write "good" software. Lots of disingenuous caveats like, "I've seen my approach work well, but maybe your solution is best for your situation." Most of that pussy-footing was born out of my own misplaced desire to please everyone. But at least some of my self-consciousness was on account of the narrative that consultants just couldn't hack it when it came to building something.

Well, I'm ready to call bullshit. Turns out, I'm better at building software than most people and, hell, most teams. If you want to get better at programming, the most important thing you can do is practice. But it wouldn't hurt for you to read or watch my stuff. 🎤🚮

Apple Intelligence summary of the abstract, which I couldn't be bothered to read:

A study comparing learners' motivations, self-regulated learning processes, and performance with different support agents (AI, human expert, writing analytics, or none) found no difference in motivation but significant differences in learning processes and performance. While AI support improved essay scores, it may also promote dependence and "metacognitive laziness."

Think of how much they saved by sending me this nonsensical content marketing collateral instead of a coupon.

Just me, or has Apple Music started giving top billing to some really weird recommendations? Every day I log in, the top recommendation is an artist I’ve never heard of, with a track or album that sounds like AI generated lofi or stock music. I admit I listen to a fair number of instrumental “Focus” playlists and channels, but I think they’re trying to do something clever with the backend algorithm and they’re failing to grasp that people use “lofi music” and “music music” completely differently.

Update: and 20 minutes after posting this, it stopped working. HomeKit giveth and HomeKit taketh away.

Out of the box, Apple’s Home app will turn on any lights you add to a scene, even if it’s only to decrease their brightness level. As a result, if your goal is to simply dim the house’s lighting at nighttime, then your scene may have the unintended effect of actually turning on a bunch of lights.

While not the best-looking app in the world, third party apps can separate a light's power state from its brightness level in a HomeKit scene, and Eve is a free one that lets you configure this.

1. First, make your HomeKit scene how you want it in the Home app, because that UI is nicer
2. In Eve, open the "Automation" view from the sidebar
3. Find the scene in the "Scenes" tab
4. For each room with a light you want to dim without turning on, tap the > chevron to the right of the room name and then uncheck each light's "Power" setting while leaving the "Brightness" setting as-is

And there you go. Dimmer lights without inadvertently turning on all your lights. 🎉

Can you catch COVID from 2020 wine?

Becky and I circled the Costco three fucking times looking for eggs before independently realizing that OF COURSE they're in the room labeled "Dairy".

Why, American people?

Having recently begun the long, arduous journey off 1Password and onto Apple Passwords, one of the biggest annoyances is how much friction it adds to the drudgery of signing into a service to have to reach behind my monitor to scan the Touch ID sensor or to ensure I’m sufficiently camera-ready for a Face ID check to pass.

Turns out, you can just turn this off altogether! I would have preferred a reasonable time-based settings like 30 minutes or an hour, but I expected the answer to be, "go pound sand," and this is indeed better than that.

Record scratch you're probably wondering how I got here.

I added string cheese to my cart, and this popped up.

Really feels like these ¥100 silicone mug toppers are trying to have it both ways.

It has been very fun and very weird to be traveling across Japan using an app that I built doing workouts designed by my spouse, but it's worked a lot better for me than fucking around with Fitbod and other apps ever did.

I can't remember getting spam issues and comments so frequently at any point in GitHub's run, so I'm not sure what's driving it now.

This morning I woke up to 40+ emails generated by a dozen or so issues splayed across a bunch of Standard Ruby's repos and initiated by five or six accounts. Unfortunately, the GitHub web UI doesn't make it easy to quickly report spam, delete issues, and block users in one fell swoop. Separately, I encountered a number of race condition bugs in their React interface that resulted in validation failures, so I wasn't able to block them all from the org. Alas.

Great way to start the day.

I have always been willing to suffer Apple Maps in exchange for its tighter platform integration than its competitors, but at least in America and Japan specifically, it has really leapfrogged Google Maps in recent years. Not only in map accuracy, but also general usability. I only today realized I could plan out multi-stop journeys. This allowed me to plan a drive from rural Kanazawa to my adopted hometown of Hikone, an Anytime Fitness in a suburb of Nagoya, a nearby Babyface Planets for dinner (fantastic Omurice btw), before eventually landing at our hotel in Shinshiro.

I'm not super comfortable driving out here, so being able to plan this out in advance to break up the trip was a huge relief and helped me stay off my phone while driving. That's a pretty big UX win.

(The fact that you can't get navigation directions in Japanese without changing your primary system language makes it less than a clean victory, however.)

Noticed an issue with Beckygram yesterday where single-video posts weren't successfully syndicating to Instagram as reels if she didn't also upload a custom thumbnail ("cover") image—which Instagram's API doesn't require.

Even though I'm in Japan with nothing but a phone, a crappy LTE signal from Google Fi (that I can't believe they charge money for), and spotty hotel Wi-Fi, I was glad to find I had the tools to fix it:

1. Log into my Mac Studio over SSH using Terminus
2. Run heroku run rails c to get into the production Rails console to reproduce the error
3. Clone the repository with Working Copy
4. Fix the bug
5. Commit & push
6. Wait for it to deploy

It was a relief this whole ordeal didn't take more than 15 minutes or so to fix and it's encouraging to know that little one-line bugs won't require me to travel with an iPad or a Mac for supporting her app in production. Nice.

(Oh, and check out her little video of Akita being cute while you're here!)