Michael Rawdon

13 Days of Halloween

Aaron’s Mahnke’s Grim & Mild is either a true cottage industry or one of the biggest names in independent podcasting, depending on who you ask – maybe they’re both! I listen to a bunch of their shows, and have tried a few others; they’re not all for me, but some of them one.

One of their projects since 2020 has been 13 Days of Halloween, which starts each year on October 19 and releases an episode a day through Halloween. I started listening in 2021 and went back to listen to the 2020 series after last year’s. This year’s series was the most ambitious – and longest – yet.

The basic framework is that the main character is thrust into an unusual environment, often with a guide of some sort, and they listen to the spookystories of the people they encounter along the way. The first season, “Hawthorne Manor”, in which the listener is guided by a caretaker (played by Keegan-Michael Key) who is searching for something in the manor, is a pure distillation of this form, in which the ongoing narrative is little more than a simple framing sequence.

The second season, “The Sea”, is about a woman who wakes up on the beach of a mysterious town and is guided by another woman through the town in a journey of discovery. (The credits on the web site do a poor job of explaining who plays who, but the two main characters are played by Kathy Najimy and Bethany Anne Lind.)

The third season, “Devil’s Night”, concerns a boy, Max (Carter Rockwood), who gets lost on Halloween night in his rural town (it’s implied this takes place in the first half of the 20th century) and is aided by a mysterious figure (Clancy Brown) as he tries to get back home through the surreal landscape.

This season, “Penance”, is about Sayuri (Natalie Morales), a young woman who is abducted and locked up in the Pendleton Rehabilitation Center without being told why. She makes friends, adjusts to life in the combination prison/institution, and over the course of many months tries to figure out how to escape.

This season breaks with the strict format of the first three seasons: Some episodes have more than one story from other characters, some have none, and some Sayuri is directly involved in. She has both higher stakes personally, and more agency, than protagonists in the previous seasons. Her personality reminded me a lot of Mallory in Greater Boston, if Mallory were placed in a scenario where she had little control over her day-to-day life. The season does have more implied violence and gore than past seasons, as far as I can recall.

Overall it was a really successful season, though I imagine the ending might be a bit divisive. I’m still not sure how I feel about it, it almost feels like it it wasn’t quite finished, but for a spooky Halloween tale maybe that was the point. It did leave me a little confused about the title of the season, though, as it’s not clear to me who was doing penance for what.

I’m not sure how they’ll top this one next year. Though I hope this is about where the length of the episodes peak; this was a lot to keep up with on a daily basis. (I’m still playing catch-up with my other regular podcasts that release episodes over the past two weeks!)

Anyway, if you are looking for some creepy, haunting tales around this time of year, keep this one in mind in the future.

Halloween 2023

Halloween seemed a little quieter this year. I didn’t write about last year (though I did write about the season in Boston a week earlier), but I thought that things were basically back to pre-pandemic levels for trick-or-treaters. Our street is pretty nuts when it comes to the flocks of kids, and even in 2020 we got about 50 kids, before the COVID vaccines were available.

We set up our usual little Halloween light display earlier in October. Walking around the neighborhood there were a lot fewer houses with lights up than in past years. I’m sure people were more motivated to put the effort in during lockdown, but really there were very few this year.

We usually buy at least 4 big bags of candy from Target or Costco each year, and this year Debbi bought a couple more than that. Then we set up our large folding table in the driveway to hand out candy. This way people aren’t constantly coming to the door, which is important because it would be constant at the peak of the evening, and neither the cats nor the dog get freaked out. (Domino spent the evening in the guest room, where I think he was mostly bored. The cats took turns looking out the front window.)

One of our neighbors came to sit with us to hand out his own candy, and a few other neighbors set up in their driveways, and sometimes we’d wander among each other to say hi.

The first couple of young kids came by between 5 and 6, and the numbers gradually ramped up until about 7:15 when it remained a pretty steady stream until 9 pm. In past years there would usually be one or two waves where there would be a crowd almost as far as the eye could see, but this year I think we maybe ended up with 10 or 12 people at once as its peak. We let people pick their own two pieces of candy off the table, which was funny because some kids would think very seriously about it, and some would pointedly take the not-chocolate ones. And then there was a girl who just said, “Whoppers are awesome!”

In the end we guess we had about 300 people pick up candy, and it turns out we overbought by maybe a third of that, so we have a bunch left over. New neighbors never believe us when we say how many people come through our street, so almost everyone else runs out before the night is over. But by 9:15 everyone’s just about done. We suspect that our street gets a lot of people because it ends at a major road and one of the houses on that corner puts up a huge Halloween display which attracts people from out of the neighborhood. Plus we have two elementary schools and a middle school nearby. But even just the next block over they get maybe half as many kids as we do.

Inflatable costumes seemed popular this year, including someone in an 8-foot-tall Garfield outfit. And while last year Wednesday Addams was the popular character (we saw a couple last night too), this year it was Spider-Man, presumably because of Across the Spider-Verse having been out over the summer.

We wound down with a late dinner and a little playtime for the dog. By bedtime there was no one walking the street that we could see. And this morning decorations were already coming down.

I’ll wrap up with one of the neighborhood houses which does put on a big display. It’s a little freaky to walk past it before 8 in the morning and have a spider jump out at you:

Halloween decorations at a house with two animatronic werewolves, a witch, spiders, and a 12-foot-tall pumpkinhead.

RIP Tim Wakefield

Tim Wakefield, my favorite Red Sox player, passed away this past Sunday from brain cancer. He was 57.

(Yes, it’s a bit unnerving to realize he was only 3 years older than me.)

I became a fan of his when he came to the Red Sox in 1995 and had two-third of a Cy Young caliber campaign. (Having him on my fantasy baseball team that year didn’t hurt.) He’d come up with the Pittsburgh Pirates and thrown almost 100 brilliant innings in 1992, but couldn’t repeat it in 1993, and got sent down and then released. A knuckleball pitcher, he relied on a pitch which was notoriously hard to control. Go read up on how baseball pitches work, and then read how knuckleball pitches work, and frankly it’s almost hard to believe any pitcher manages to throw strikes with them with any regularity.

It’s easy to love the great sluggers like Albert Pujols (and I do love Albert Pujols), but I also love the quirky players who bring something unusual to the game. Ichiro Suzuki’s unbelievable ability to make contact. Mike Boddicker’s ridiculous curveball. And Tim Wakefield having an almost 20-year career in the Majors throwing a knuckleball.

One of my enduring baseball memories was attending the Red Sox/Twins game on July 24, 1995. This is the only time I recall attending a game at Fenway where I sat in the bleachers. Wakefield started the game and gave up a triple to Chuck Knoblauch. He then struck out the next two batters, while Knoblauch danced around third base. Finally, while facing the next batter, he looked over at Knoblauch and cocked his head towards home plate, saying “If you’re going to go, then go.” Knoblauch went, and Wakefield threw him out on the steal attempt. Presumably on the knuckleball, since he rarely threw anything else, although he did occasionally throw a “fast” ball which was probably slower than most pitchers’ breaking balls.

The other memorable moment was in a game I didn’t watch, since I refuse to watch Yankees playoff games, and none more so than the 2004 ALCS. In game 3, the Yankees were tee’ing off of Red Sox pitching, to the tune of 10 runs in 3-1/3 innings. While the Sox were not completely out of it, Wakefield came in and threw 3-1/3 innings himself, giving up another 5 runs but likely helping save the rest of the pitching staff for the team’s historic comeback over the next 4 games.

Wakefield supposedly had a team-friendly contract which got renewed every year until the end of his career. I haven’t been able to find details of this deal, so maybe I imagined it, but as a very durable mid-rotation starter and long reliever, he probably appreciated the job security and he objectively made plenty of money while being able to stay with the Red Sox for the rest of his career. Sometimes it’s not all about the money. And he did win 2 championships with them.

Although he never got the attention of David Ortiz, Pedro Martinez, Manny Ramirez, or other star players, Tim Wakefield was an ever-present part of the Red Sox for a really, really long time, baffling pitchers (and catchers) with his ridiculous stuff.

Thanks for everything, Tim.

Everyday Monsters

There are a couple of webcomics artists I’ve been enjoying tremendously, though both of them update only sporadically, presumably because this is a hobby for them and they both have lives which take most of their time. They have a common theme of what I’ve been calling “everyday monsters”, as they primarily feature nonhuman (or formerly human) beings in dark fantasy environments, but emphasizing the everyday lives and concerns of those beings

Both of them (coincidentally?) primarily post on Instagram and Twitter. Both of them post anonymously and have very little Internet presence beyond these sites as far as I can tell.

Pocketss (Instagram, Twitter) has “i like to draw fantasy nonsense” as their Twitter profile description. Their work has a running theme of people (or whatever) caring for other people. For example this strip about a swamp dweller who sees a passer-by carrying a lantern on a stock. Or this one about goblins looking out for each other.

There’s also a cute running story – starting here – about a witch who invites a harpy to a girls’ night party, throwing the harpy into confusion and anxiety. Poor harpy!

My favorite one, though, is this one about a vampire (?) who orders her thralls to leave her alone so she can… well, go see for yourself.

Vampire: "Begone, thralls! Leave me to my evil and sexy affairs..."

Pocketss also has a Patreon which I just signed up for.

Saint Monster (Instagram, Twitter) has “Monsters need love too” as their Twitter description. Ironically their work features far more actual humans than that of Pocketss, and a few more recurring characters. For example the halfling apprentice witch, who later appears here. Or the trio of human, elf (?) and goblin (?) travellers, who appear here, here, and have their best moment so far here.

But the strip that maybe best sums up their work is this one about a researcher who runs into a Sphinx.

Sphinx: If you wish to pass you must first answer my riddle, And should you fail, you will not leave here alive.

Researcher: I have studied the enigmas of Alatosh and Zanzibar's thousand mysteries. Ask your riddle, Sphinx.

Their Twitter account has some fan art and a few other pieces by them besides the full strips which are also on Instagram. No Patreon, though.

I love both of these artists and hope they both get to a place where they can produce work more regularly.

A Month of Maintenance

More like a month and a half of maintenance, to be frank.

Since we got back from Massachusetts in mid-July, I’ve spent sizable chunks of my weekends doing home maintenance and improvement.

The big thing we did was to buy a new dishwasher. Debbi never cared for our old GE dishwasher, and while I thought it was okay, I admit it was loud. And it didn’t always do the best job of cleaning things. Maybe it wasn’t so okay. But the forcing factor was that it started leaking: We’d occasionally find a bunch of water at the bottom of the machine, or worse, on the kitchen floor. And our cat sitter got to clean up a spill while we were away. So it was time. We replaced it with a Bosch SHP865ZP5N from Airport Home Appliance, which is where we bought our refrigerator two years ago. We’re pretty happy with the no-nonsense experience we’ve gotten there, as well as the ease of delivery and installation.

Installation did come with one little hiccup: The valve for the water at the wall was stuck and had to be replaced, which was not cheap. A little annoying since they basically had us as a captive audience for the installation. They said these valves break all the time because they’re all pretty cheap these days. Someone on Facebook suggested we should test them all every year, but it’s not like I want to replace them myself, or hire someone to come out and replace any ones which stick. Still, this valve lasted about 15 years, which doesn’t seem too bad.

Most of my other work has been in the yard. Our yard is pretty nice, but it’s about 15% larger than I have the time and energy to care for, so projects have built up over time. Consequently, I’ve spent a few hours each weekend cutting back the jasmine, trimming the rosemary, and pulling up tree seedlings and blackberry vines. The plum tree has suddenly decided to produce a whole bunch of plums this year, which caused many of its branches to start leaning to one side, so I gave it a good pruning, too. The plums are not great, and there was way more than we could eat even if they were great, so I’ve been raking them up occasionally, but they’re pretty messy. I’m also getting ready to start trimming back the fig tree which has been slowly growing over our fence since we moved in.

I also cleared out a space and bought six cubic feet of dirt to start a dirt pile for Domino to dig in. I probably need to buy another six-to-ten cubic feet to make it really satisfying, but it’s a start.

Then last weekend I give our bathrooms a good deep cleaning, mopped the floors, and scrubbed the floor of the master shower, which it really needed. So they’re just about as clean as they’ve been since we moved in. I also want to mop the kitchen floor.

Then I took my car in for its annual maintenance, where it needed its serpentine belt changed. It also has a leak which is likely around the seals for the convertible top (some might remember that I have a Volkswagen Eos), and is going to be expensive to fix. So I decided to defer that until we get closer to the rainy season.

Car ownership seems like it’s gotten a lot more expensive in the past decade! Or maybe it’s just the difference between Hondas and VWs.

We’re also coming out of a long stretch of warm weather, after a stretch of what seemed like cooler-than-normal weather. Globally, July was the hottest month on record. Here in my hometown:

In May, we had highs in the high 60s (°F) in the first third of the month, highs between 70 and 85 in the second third, and in the low 70s in the last third.
In June highs were in the 70s almost every day until a spike at the end of the month – which I was back east. These are what I recall were typical summer temperatures when I first moved here.
I was gone for the first third of July, but highs were consistently in the 80s for the rest of the month.
And August was more of the same, with several spikes in the low 90s, and a few days with highs in the high 70s. And the overnight lows were stubbornly above 60 for about half of the month. It was also unusually humid, with dew points in the low 60s a number of times, which is nothing for places where it gets genuinely yucky, but it’s unusually moist for here.

So July and August were both hot. Yard work on some of those days was no fun, I’ll tell you. And our electric bill was not much fun either, thanks to the air conditioner. (Someday we’ll put in solar panels!)

(My data comes from Weather Underground.)

Out of curiosity I checked June-to-August for my first 2 years here, and my recollections match the data: Highs mostly in the 70s, with a few spikes along the way (though the data for 2000 looks untrustworthy).

Anyway, that’s enough of that; I’ll leave the deeper dives on historical temperatures to J.D. Roth.

We’ve also been having some challenges with Domino, in particular that he hasn’t wanted to sleep in his crate at night, panting and whining when we put him in there. We suspect he had some unpleasant event in there – maybe even just a bad dream – but it’s meant that Debbi has been sleeping with him in our guest room until we can figure it out. They’re going to see the vet soon to see if there’s anything physically wrong, though he’s been about the same in all other ways. Hopefully he’s okay, but it’s been frustrating.

Speaking of frustrating, I’ve also been dealing with both (self-diagnosed) plantar fasciitis and achilles tendinitis in my right foot. It’s been gradually getting better – the new running sneakers I bought have helped a lot – but not as fast as I’d like. I should probably look into some exercises to help with them, too. (Also: For some reason New Balance running sneakers run smaller than their walking sneakers. Shrug.)

So that’s been my summer, not counting work, since I rarely blog about that. I have spent most of the past week at work working on improving some long-neglected but still-useful code I’d been thinking about for a while. It’s been fun.

Hopefully we can continue to dodge COVID until we can get new boosters this fall, and otherwise enjoy some cooler weather this month, starting with this long weekend.

Rainbow over Mountain View, August 13, 2023
Rainfall was negligible
This photo doesn’t really do it justice

Star Trek: Strange New Worlds: Seasons 1 & 2

Star Trek: Strange New Worlds is a spin-off from Star Trek: Discovery, in the second season of which Captain Christopher Pike (Anson Mount) takes command of the Discovery after the Enterprise has been damaged, and it wraps up with the two ships and their crews teaming up to save the day. This series takes place about 7 years before the original Star Trek series and chronicles the adventures adventures of the Enterprise under Pike, who is living with the knowledge that he is destined to be crippled saving several crewmen a few years in the future.

The Enterprise bridge in Strange New Worlds

The elevator pitch for this series is basically, “If you want more of the original series, with better effects and updated for modern social sensibilities, then this is the show for you.” It’s not nearly as good at this – or as good overall – as the Star Trek: Year Five comic book, but it’s enjoyable.

Early on in watching this show I decided to embrace something someone suggested on Twitter: That each Star Trek series takes place in its own continuity, even though it pretends to maintain continuity with the other series. SNW has this quality in spades, with lots of nods to the original series, which don’t stand up to even casual examination. After enough continuity-jarring moments involving Spock or some other character or alien race who appeared in the original series exhibiting very different behavior or characteristics in SNW, it just becomes easier to treat the two shows as being in different continuities.

But once you get there the show is an enjoyable episodic sci-fi romp with a few excellent episodes and a few poor ones. The acting is stronger than usual for a Star Trek show. It still contains all the pseudoscientific nonsense one expects from Star Trek, there’s not much of an ongoing storyline, so it’s hard to get too invested or too disappointed.

Spoilery thoughts after the cut:

What Bluesky Needs

Back in January I wrote a post titled “What Mastodon Needs”, about what I felt were the most serious shortcomings of that social media platform after I’d been on it for a couple of months. (Some of those issues have been resolved by my settling on Ivory as my Mastodon client, but others remain stubbornly unresolved, joined by new ones such as a lack of quote-reposts.)

I thought it’s time to write one on the other would-by Twitter replacement platform I spend some time on, Bluesky.

Full transparency: I find Mastodon a lot more useful and enjoyable than Bluesky. But many people are the other way around. Indeed, when I see someone compare the two, it’s almost always in Bluesky’s favor. Last month I made the following observation:

Post by me on Bluesky: "There's no better testament to the fact that it's community rather than platforms that makes social media work than that the platform experience on
Bluesky - app, features, bugs - are pretty terrible (IMO) yet the community is vibrant."

There are also people who have found Mastodon to be a mixed-to-negative experience. I could pull a number of examples, but here’s a particularly prominent one from today:

Bluesky post by Neil Gaiman: "It's hard to explain why I don't enjoy Mastodon. But it's all encapsulated perfectly in this perfectly-normal-for-Mastodon conversation."

(see next image)

Neil Gaiman post about how he feels when his books are banned is replied to by an anonymous user with: "A pro library post with a quote about how I feel when my books are banned is replied to with
"Mmhhh... This unicorn mindset doesn't really fit with Mein Kampf, though."

All of this is fair enough. And Bluesky does have a few significant detractors, often people with problems with its ownership. Which is also fair enough. After all, I’m not on Threads because I don’t really want to get deeper into the Facebook ecosystem.

Anyway, my main goal here is to hit major points of usability where I feel Bluesky is lacking. And I should be clear that I realize that Bluesky is a platform which is still in beta (indeed, it feels like it’s not quite ready for beta and I suspect it opened up before it had planned to), is still invitation-only (only users with invite codes can invite new users), and reportedly has very small development team. So I expect progress will be slow, and it’s starting from a point of being much less mature than Mastodon.

So here we go:

1. Lists: I’ve been an avoid user of lists on both Twitter and Mastodon. I have a dozen or more lists which I use to divide up accounts I follow by category, saving my main timeline for accounts I either want to check in with whenever I check in on the platform, or which don’t fall into a category. But, for example, I put most Magic: The Gathering accounts, or audio drama accounts, into their own list. And I remove them from my main timeline. (This last point is something neither Twitter nor Mastodon supports natively, I think, but some apps like Tweetbot did and Ivory does.)

Not having lists is likely to impose a strong cap on how many accounts I follow. This isn’t an issue yet (I’m following only 39 accounts – Bluesky is still small, folks), but it will be if the site gets popular.

2. Remembering my reading position: This was a bullet point for Mastodon, and it’s a problem on Bluesky, too.

3. An iPad app which doesn’t suck: Presently the iPhone app runs on the iPad in compatibility mode, which is frankly pretty lousy – especially because it’s pretty buggy and its UX is not very polished. Instagram also has the problem of no native iPad app, but it’s not as much of an issue there because Instagram is image-centric.

4. Disabling reposts per-user: Some people repost a lot. Which is fine – people can do with their accounts what they want. But I find being able to disable reposts for a few users significantly improves my experience on social media, when I enjoy the personally-written posts by those users but mostly find their reposts to be a fire hose of things which are way more important to them than to me. Right now my only option is to mute them entirely (which I have done a couple of times).

Related to this is being able to mute a user (or a keyword!) for a day, a week, or a month, since sometimes people get focused on something which is time-bound which doesn’t interest me, but once that time is passed I want to resume following them.

These are little things that Twitter and/or its third party clients provided which turned out to be indispensable to enjoying it in the long run.

5. Bookmarks and a way to see your Likes: Mastodon has both Likes and Bookmarks. Bluesky has Likes but no Bookmarks, and as far as I can tell there’s no way to view a list of the posts you’ve Liked.

6. Hashtag support: This would be a more useful way to find like-minded people and posts than Bluesky’s feed system, which my experience with so far has found it to be pretty clunky.

The other big problem is one I think all social media sites going forward will have: Fragmentation of communities. The tech community is mostly on Mastodon, the science fiction and comic book communities are on Bluesky, and the Magic: The Gathering and audio drama communities are still very sticky on Twitter (or, as I like to call it after its X rebrand, Shitter). There probably isn’t a “solution” to this, it just means that people like me who follow multiple communities will need to be on multiple platforms.

Anyway, Bluesky does have a fair bit of fun stuff happening (and not all of it revolving around Neil Gaiman, John Scalzi and Popehat), it’s just that the platform itself makes it difficult for me to interact with. I hope it gets better, but I’m not going to hold my breath for that to happen.

Firmament

Earlier this summer I played Firmament, the new puzzle game from Cyan, the creators of Myst.

I love these sorts of games, and I wrote about what I like about them a few years ago in the context of Zed. I enjoy a mix of puzzles, setting, and story, which Cyan has historically been good at providing. I backed Firmament on Kickstarter as soon as they announced they’d be doing a Mac version, having also backed their previous game, Obduction, which I enjoyed a lot, though I thought it had a few flaws.

Firmament modifies the traditional point-and-click interface with a device the player uses called an Adjunct, which they use to connect to sockets throughout the game which provides some additional flexibility in how the player interacts with the world. It also both makes it clearer what you can interact with, but it feels somewhat limiting since everything has some small variation of the same interface. I’ve seen it theorized that the Adjunct mechanic was created to make the VR experience of the game better or more consistent or something. I guess it’s possible, I dunno. Maybe that was a concern 4 years ago when they started making the game?

A spoiler-free review first, and then some further thoughts:

The setting for Firmament is that you wake up from long-term sleep and are greeted by the Mentor, who appears to be a ghost of your predecessor. They’ve woken you up and advise you from time to time. The world consists of three settings, an ice zone, a botanical garden, and a sulphur-based power plant, along with a central structure1 called The Swan. You travel between them via conveyance pods, and have two waves of tasks to accomplish on each world to get to the conclusion.

There are basically three sorts of things in these games that I dislike: Puzzles that are too hard (this is obviously subjective), having to walk back and forth a lot to solve a puzzle, and things that are hard to see. Firmament has a few spots where there were things I just couldn’t see and I had to use a walkthrough – a video one in one case – to figure out what I was missing. This is frustrating because it feels like I just was never going to figure it out on my own. The game does pretty well on the other two points, although there was one puzzle I didn’t so much figure out as stumble into the answer for. Better lucky than good, I guess?

The game’s weakness, I think, was its story. Since Cyan’s games are solo endeavors with little capability for you to interact with anyone in the game, they all take place in environments where the people who used to be there are gone, and finding out what happened to them is part of the adventure. Firmament feels pretty thin, here, as the Mentor and one other character are the only ones you learn much about. There were clearly more people around, but we learn very little about them. I think they could have threaded more characters and more events into the game and provided a richer story to explore. As it was, it definitely felt less sophisticated than Obduction.

(I’m inclined to think that the use of AI to assist in generating parts of the game are not really at fault as this article thinks they might be. I think they just didn’t spend enough time coming up with enough story to make it satisfying.)

I think the game took me about 15 hours to complete. I did run into one bug, but it turned out not to affect me in that puzzle. Other people have run into more serious bugs, but they’ve been fixing them. If you enjoy games like these, give this one a try, but temper your expectations, especially if story is your main interest.

A few more spoilery comments after the cut:

What Next With COVID?

As I said last time, it seems like just about everyone has put COVID behind them in their behavior: Hardly anyone is masking or physically distancing anymore, and I don’t see many mentions of it other than on social media from the few people who are still taking those precautions.

I see close to zero reports these days of how many cases, hospitalizations or deaths there are from COVID. Since it’s been over 9 months since the last boosters were authorized, and previous evidence was that boosters lost most of their effectiveness after about 6 months, I was wondering what the numbers are.

Today the San Jose Mercury News published this article: New record lows for California COVID hospitalizations. Will it stick?

The number of patients with the virus at California hospitals reached a new low this month since the start of the pandemic, with just 611 reported on July 2.

Statewide, before this summer the previous low was 1,170 people hospitalized with COVID in June 2021. Now, totals have been less than that since early June.

In November 2021 I wrote a piece here titled “This is as Good as it’s Going to Get”. When I first drafted this post I thought it held up pretty well, and was maybe a bit optimistic. But based on the Mercury News article it’s looking a bit pessimistic, at least for the general population; the spectacular failures to support people such as the immunocompromised have been well documented.

I do find this a little surprising: The Omicron variant and its many sub-variants are the dominant strain of the virus, are massively transmissible, and haven’t gone away. But maybe they’ve been evolving to be less severe, and maybe the spotty vaccinations we’ve had have been good enough to gradually suppress the virus. I dunno.

Another thing I saw recently is this thread on Mastodon:

Mastodon post by Pavel A. Samsonov (1/2):

Techies perennially yearn for an org culture where their pure, intellectual work is cleanly separated from meetings and politics, where ideas win on their merit and "the work" is entirely solving technical problems.

Such an environment cannot exist, for 2 important reasons.

Mastodon post by Pavel A. Samsonov (2/2):

1 There can be no universal benchmark that defines "the best idea." When people get together to decide on the best thing to do - that's called politics. This goes for both solutions and problems. A brilliant solution to an irrelevant problem is bad.

2 The merit of a solution is 1% cleverness and 99% execution. Something that is out there and working suboptimally is "better" than an elegant idea that never got off the ground. Measuring on intellectual purity alone asks us to ignore actual impact

The first post is context, but the second post applies as much to our COVID response (as a society) as it does to the original topic:

People aren’t masking, they’re not physically distancing, and many people are not getting boosters and wouldn’t even if they were available. (And that’s just in the United States. I imagine it’s similar but more so in countries where those things are actively hard to do.) None of that is likely to change unless the current environment significantly changes. While encouraging people to do those things – especially getting vaccinated, which is a very low-intrusiveness part of the solution – is fine, any real solution is going to have to be implemented in the context of how people are behaving and are likely to behave. Because a solution which can’t be implemented is not a solution.

Personally, I’d like to see the FDA authorize twice-a-year boosters for everyone and encourage people to get them. And I’d like to see tests be made more widely available and covered by insurance so people don’t need to worry about access to them. (More info about how reliable they are would be nice, too. Last I heard tests were only about 60% accurate against Omicron.) I think those would be the most effective first steps, followed by covering wages for people who have to skip work because they get sick.

Alas even that seems like a stretch in the current political climate.

Tumultuous Trip

We’re back from a week and a half vacation to the east coast. It was… quite a ride, enough that I kinda feel like I need a vacation to recover from my vacation.

I don’t often talk about it here because it feels like not-so-humble bragging, but we have a vacation house in Massachusetts. It’s in a pretty great location, and we bought it to keep it in the (extended) family. We got a pretty good deal on it, but we learned a couple of years ago that part of the reason for that is that it needed some deferred maintenance. We hired a really excellent contractor, but the project kept getting bigger for various reasons, and ultimately it turned into a major remodel, which is just now finishing up.

Our trip back in May was partly to try to finish preparing the house for this trip. We found that there was more to buy than we’d expected, and so we’d planned to spend the first couple of days on this trip buying and assembling furniture, and unpacking the house.

The plan was to fly out on a 6 am flight on Tuesday, June 27. We were going with friends of ours and their kids, to spend about 2 weeks at the house.

Everything went sideways when Debbi and her friend found out around 11:30 pm that our flight had been cancelled due to extreme weather on the east coast. Worse, we weren’t able to rebook until Thursday. So we spent a couple of days kicking around home before we were able to leave. And even then our flight was over 2 hours delayed. We landed in Boston a bit before 11 pm. On the bright side, the rental car kicks are pretty quiet at that hour, so we were able to get our cars smoothly and get down to the house by 12:30 am. We spent an hour and a half looking around (and figuring out how to turn the lights off) before going to bed.

Unfortunately this meant we’d lost over 2 days of prep time, so we had to shuffle around and compress the work we’d planned to do. We went to IKEA and Target on Sunday, assembled furniture over the next few days as time permitted. Especially on July 3, which is when the area where our house is holds its Independence Day celebrations, presumably because people want to drink and then sleep in on the Fourth. (Because when people are shooting off fireworks, you definitely want those people to have been drinking.)

Among this I also mixed in a number of trips to visit my Dad. His story isn’t mine to tell – I don’t think he’s ever been very comfortable with me writing about him online – but he’s needed assistance from me and my sister Katy recently. So I made several trips up to visit. But I also got to see my sister and nephew, who came down one day to see our house. Seeing them all was nice, but it was a hectic time.

We also spent a lot of time with Debbi’s family, who all came over at various times to visit. I missed seeing a couple of them because I was off taking care of business. Maybe next time.

The weather was a little iffy, always warm but not too warm, but with humidity that came and went, and showers from time to time. We did get a few nice days to spend at the beach, though.

Our friends left us on the second Friday to spend the weekend in Boston, which they wanted to play tourist in. So Debbi and I had a quieter weekend. But it turned out my friend Karen and her beau were also visiting Boston this weekend, so they came down on Saturday to hang out. We hadn’t seen each other since before the pandemic, and it was great to see them.

Speaking of the pandemic, it’s clear that almost everyone has put it behind them at this point. Few people were masking anywhere we went, including in airports, and no one was physically distancing that I could tell. We wore masks a bit for the first few days and then ditched them. I’ll likely write something else about this in the near future. I am looking forward to getting another booster, though, and wish they’d make them available to everyone twice a year.

The trip ended, unfortunately, with another flight delay. We didn’t get back to San Francisco until nearly 11 pm on Monday night, and were totally exhausted by the time we got home and went to bed. The cats were really, really happy to see us, of course, and our friends who care for Domino when we’re away were happy to keep him a couple of extra days so the cats could have some dedicated time with us. But of course he was really happy to see us, too.

Anyway, it was a good, productive trip, but not very restful. Hopefully we can do something lower-key later this year. Once we recover from all this air travel.