Author: Andrew Huey

more about media consumption

I’ve been blogging recently about how I’m watching football this year, and stuff like that. I’m continuing to think about that, plus going beyond that to more about media consumption in general.

Right now, I’m watching NFL RedZone for my Sunday football fix. Later tonight, I’ll watch the Giants game on Sunday Night Football, via Peacock. That’ll actually be the first Giants game I’ve been able to watch on my TV this season. (I did watch a bit of last week’s game on my iPad, which I can do with my NFL+ subscription.) This is all fine for now. I’m getting my fill of football. Depending on how the Giants do, I may get either more interested or less interested in the weeks to come.

I briefly mentioned the Colbert thing a couple of weeks ago. Now we’ve got the Kimmel thing too. I haven’t canceled my Disney+ subscription, though I support anyone who’s doing that. I’ve been thinking about how I should react to this stuff, and have decided that maybe a positive reaction is a better choice for me.

For instance, I’ve been listening to The Bugle for years. It’s a great podcast, with some great political humor. So I went ahead and signed up for a £50/year subscription/donation. I probably should have done that a few years ago.

I’m also looking at revising the way I consume news a bit, and maybe supporting some publications/sites/podcasts that I haven’t been reading/supporting/whatever. Weirdly, I seem to keep coming back to the idea of signing up for Apple News+. A lot of the publications I’m considering supporting are available on News+. I know that giving Apple that money won’t result in very much of it making its way to whichever publication I’m reading, but it would be convenient. On the other hand, it’s not available on Windows, and I’m not sure it would fit well into my usual workflows for reading and bookmarking stuff.

I think maybe the way forward is to support independent media, whether it be news or comedy or whatever. Big business has consistently shown that it’s more interested in being on the government’s “good side” than it is in accuracy, morality, or freedom of expression.

NFL Sunday

So here’s some notes and thoughts about my experience trying to watch football today, the first Sunday of the football season.

As I’ve previously mentioned, I don’t have any “traditional” TV service this year, having discontinued YouTube TV. But I ponied up for NFL+ Premium and the new ESPN Unlimited service.

So, for pregame shows, I was switching between the NFL network pregame show and the ESPN one. Both are reasonably good. One thing I hadn’t considered about this setup is that I no longer have anything resembling a DVR; I can’t pause, fast-forward, or rewind any of this stuff. And it’s harder to switch between “channels”, since I’m now switching between apps.

For the actual games, I decided to try watching NFL RedZone. That was actually pretty cool; I’d never had access to it before. It’s a little too “busy” for me; I’d rather see more of each game and less switching back and forth. But it’s fun and really gives you a lot of coverage of all the games.

There was a lot of grumbling recently about the announcement that they’d have commercials during RedZone this year. What I saw wasn’t really a big deal though; I think there was one very short commercial during the whole first hour of RedZone.

Speaking of commercials: another thing I miss about not having any DVR ability is never being able to fast-forward through commercials. I was watching NFL Matchup on ESPN this morning, and, despite it being a show I was watching on-demand, there were commercials in it and no way to skip them. I may be misremembering, but I think, in previous years, whenever I’d watch NFL Matchup via ESPN+, it would be commercial-free.

The Giants and Jets have, of course, both lost their first game. I don’t think this is going to be a good year for the Giants, but hopefully it’ll be better than last year.

messing around with Firefox and Vivaldi

My usual browser setup, for a while now, has been to use Firefox on desktop and Safari on mobile. (I have my bookmarks syncing between Firefox and Safari with iCloud for Windows.) That’s worked out pretty well, and I really have no complaints. But, of course, I’m a nerd, so I have to mess around with things once in a while, even if they work well.

So my first experiment was to see if I could switch to Firefox on mobile, so I’d be using Firefox everywhere. That’s been working well, though there are some tradeoffs. Apple, of course, puts every browser on iOS except Safari at a disadvantage, in several ways. The most obvious one is content blockers, which only work with Safari. I use 1Blocker on iOS, and that works reasonably well, but not nearly as well as uBlock Origin on desktop. With Firefox on iOS, I guess that their Enhanced Tracking Protection helps a bit, but it would be nice to have real ad blocking.

My next experiment has been to see if I could switch from Firefox to Vivaldi. I haven’t gotten too far with that, and I don’t know if I’m going to stick with it. I have Vivaldi set up on all of my main devices now: Windows desktop, MacBook Air, iPhone, and iPad. Vivaldi does do ad-blocking on iOS, since it’s got built-in ad-blocking. I’m not sure if it’s all that great though. I need to use it some more and get a feel for it.

One issue I’ve been having with Vivaldi is their settings sync. In theory, all of the settings should sync between all the installs of the browser, but that hasn’t worked out perfectly. The ad-blocking exception list doesn’t seem to sync at all. Another one is that my search setup doesn’t sync correctly. There seems to be a workaround, but it’s not perfect.

Speaking of search, I’ve been sticking with Kagi. I first started using it earlier this year, and I’m liking it. Of course, setting it up in a new browser can be a hassle, since you need to be logged in to use it, and since it’s not on the list of default search engines in any major browser.

So, overall: I’m going to continue messing around with Vivaldi a bit, but I might give up on it. If I do, I don’t know if I’ll go back to using Firefox everywhere, or my old system of using Firefox on desktop and Safari on mobile.

 

sports, eyesight, and other stuff

I’ve got a list of stuff I want to blog about. I’m not sure how far I’ll get, but I’m going to try to cover a bunch of stuff.

Sports & streaming

My last post, from two weeks ago, went into a lot of stuff around my plans for watching sports on TV this fall. Not much has changed there, except that I gave in and signed up for another one-year Paramount+ subscription, since they just started a 50% off deal. So now I can watch any of the CBS NFL games on Sunday, though that’ll mostly be the Jets rather than the Giants. And I can also watch the new season of Strange New Worlds.

I’m still not happy with Paramount, after the Colbert thing, and the more recent Bari Weiss thing, and… other stuff. But I guess my protest against them is only going as far as refusing to pay full price for a Paramount+ subscription.

I’m still holding out on Fox though. I haven’t even really been tempted to sign up for a Fox One subscription. That would be a step too far.

My plan for tomorrow, the first Sunday of NFL season, is to try to watch NFL RedZone (via NFL+) and see if I like it. (And, of course, annoyingly, this is the season when they’re going to start running ads on RedZone. Oh well.)

My eyesight

I had a little incident about a week ago, where I got a new floater showing up in my left eye, and that brought on a migraine. I wasn’t sure if this was the return of my migraines from ten years ago, or something else. Long story short, I saw my eye doctor and she sent me to a retina specialist, to see if I needed laser surgery. And that specialist poked and prodded my eye and decided I don’t need surgery. Which is good, I guess, but it also means that I’m stuck with the floater, which hasn’t quite gone away. I don’t notice it most of the time, but it’s somewhat noticeable when I’m working on a computer (and unfortunately, I make my living sitting in front of a computer). So we’ll see how things go. Maybe it’ll go away?

Switching cell phone service providers

I’ve been a Verizon customer since I got my first apartment after college. Back then, it was Bell Atlantic, and it was for a POTS line. And when I got my first cell phone, it was on Bell Atlantic Mobile. That all got smushed together into Verizon at some point. So, basically, I’ve been paying a Verizon bill every month since 1989 or thereabouts.

So there’s a lot of inertia there, and it wasn’t easy for me to talk myself into considering switching to another provider. But there have been some issues that had been pushing me in that direction for a while now.

First, they cut the copper to my apartment building (in 2018) and cut off the POTS service. After that I switched to a home cell service thing, but cancelled that last year, and “parked” my home number with Park My Phone, forwarding it to my cell #.

Then there was the issue we had in the office, starting about a year ago, where Verizon cell service deteriorated to the point of being essentially unusable. (It’s gotten better since, but still isn’t great.)

And also, I’ve found out that the Verizon discount I get through work is limited to my old “legacy” plan and doesn’t apply if I switch to a new plan, with a higher data cap (or unlimited data).

So, after a lot of hemming and hawing, I finally decided to switch to Consumer Cellular. They’re an MVNO for AT&T, and I knew from coworkers that AT&T service in our building is fine, so that was one selling point. (I have, in fact, found out that it’s not just “fine”, but significantly faster than even my home internet service.) And it’s a lot cheaper, even with a bigger data plan. With Verizon, I was paying about $65/month for 5 GB. With Consumer Cellular, I’m paying $35/month for 10 GB. There doesn’t seem to be any downside, as far as I can tell.

Well, that’s about half of the stuff I wanted to blog about. Maybe I’ll write more tomorrow, if the football is boring, and if my left eye isn’t bothering me too much.

more nonsense about sports and streaming

This is the third post I’ve written about sports and streaming this month. (See here and here for the previous ones.) Sorry. I guess I’ve been retreating into watching (and reading about) sports because the “serious” news is too stressful right now.

I mentioned the new ESPN streaming thing in one of my previous posts. I gave in and signed up for it yesterday. My previous Disney+ bundle was the “legacy” one that included ad-free Disney+ and ad-supported Hulu. That was $22/month. There’s no equivalent bundle with the new ESPN service. The bundle with ad-supported Disney+ and Hulu is $30/month. The bundle with ad-free Disney+ and Hulu is $39/month. So I went ahead and signed up for that. It’s probably too expensive, and I don’t know if I’ll stick with it. And that $39/month rate is a promo; after a year, it goes to $45/month.

It just seems like all of this stuff is getting too expensive and too complicated. I’m still pretty happy with my MLB.TV subscription, which lets me watch most of the Phillies games. (I wish I could watch all of them, but I guess it’s good enough.)

I’m still not sure if I’m going to be happy with my NFL situation this season. I’m still planning on watching RedZone on Sundays (via NFL+) and hoping that’ll scratch my football itch. And I can watch Thursday Night Football on Amazon, Sunday Night Football on Peacock, and Monday Night Football via my new ESPN subscription. So that should be enough.

I’m also trying to see if I can get into Premier League Soccer. I was randomly clicking around in the Peacock app last Saturday, and happened to notice that it was week one of their season. And Peacock has a whip-around show (similar to RedZone I guess) called Goal Rush, so I can watch that for a couple of hours on Saturday and see bits and pieces of a few different games. So now it’s week two, and I’ve watched a bit of this stuff, and it’s kind of fun, though I’m mostly treating it as background noise. I haven’t developed any real interest in it yet.

And I briefly thought about giving up on the NFL and following the CFL instead. That thought came from the storyline that ran in the Crankshaft comic strip recently, where the main character went to Winnipeg to see a Blue Bombers game. It turns out that streaming rights for the CFL in the US aren’t terribly complicated, but they’re not terribly convenient for me either. Some games run on CBS Sports Network, which I’d probably have if I still had YouTube TV, and which might be included with Paramount+, though I’m not sure. The rest of the games can be watched on CFL+, which is a free streaming service. So that sounds good! It’s free! But there’s no Apple TV app. I’d have to pull up the website on my laptop and then AirPlay it to the Apple TV. That’s too much work.

So overall, my plan for distracting myself with sports for the next few months is approximately as follows:

  • Phillies games on weeknights, via MLB.TV.
  • Some other random baseball games on ESPN and Apple TV+.
  • NFL games on Sunday via RedZone on NFL+.
  • Thursday, Sunday, and Monday night football via Amazon, Peacock, and ESPN.
  • Maybe Premier League soccer on Peacock on Saturdays.

This will probably all fall apart at some point. If the Giants are as bad as they were last year, I may lose interest in the NFL. Or, conversely, if they do well, I might get frustrated about not being able to watch all of the games.

And I don’t even want to think about how complicated watching the MLB and NFL playoffs will be. Well, that’s a problem for another day.

playing with AI and enjoying sports

OK, so that’s two completely different topics, but I’m going to throw them together in one post. I’ll start with AI.

At work, I’m still very limited in the AI tools I can use: basically, just Copilot and our own internal chatbot. (And it’s just the plain Copilot chat that I can use, not GitHub Copilot.) I’ve been wanting to experiment with some of the coding tools that are out there, so I decided to try some stuff out on my (personal) laptop. I was going to try Claude Code first, but I decided that GitHub Copilot would be easier for me to set up.

I started by enabling it in my personal GitHub account, and setting up the extension in Visual Studio Code. Then I tried something simple: asking it to write a “hello world” console app in C#. It did that successfully, but of course that’s a pretty low bar. I then tried to get it to help me create a git repo for the project. That worked, but it didn’t create a .gitignore file , so all of the binary output files got added to the repo. When I pointed that out, it apologized and created a .gitignore file, but it didn’t really offer me any help with cleaning up the mess it created. And, while the .gitignore file it created was “good enough”, it was a little questionable.

So I stepped back a bit, deleted the git repo and the .gitignore file, and tried again in Visual Studio 2022. I went through the usual steps in VS 2022 to initialize a git repo, and that created the usual VS .gitignore, so that was a lot cleaner than what Copilot did. Then, I set up Copilot in VS 2022. It probably works a bit better in VS 2022 over VS Code, at least for me.

I had Copilot in VS 2022 make a few little changes to the program to see how it worked. I had it add a line to output the current date and time, and that was simple enough. I then had it add some code to show the operating system and version, and that was a bit dicier. I had to coach it through making changes so that the program would actually output “Windows 11 Pro” instead of Windows NT or Windows 10.

So my opinion on this stuff hasn’t changed much. It’s interesting, and can be useful, but it’s wrong about half the time, and it’s often no more efficient than just doing an internet search and copying something from Stack Overflow. I kind of want to try it on something bigger, but I’m not sure what I should try.

On the sports topic: as per my last post, I signed up for NFL+ Premium recently, and have been watching some preseason football. The annual Jets/Giants preseason game is tomorrow night. That’s usually fun.

I’m still not sure what I’m going to do about the new ESPN service. I’ll have to look at the price for switching my Disney+/Hulu/ESPN+ bundle to include the full ESPN.

And I’m still planning on skipping the new Fox service, on general principle. Which is a bit tough, since the first two regular season Giants games are on Fox, so I won’t be able to watch them. My plan, for now, is to watch NFL RedZone (via NFL+) on Sundays and see if that’s good enough to keep me entertained and show me enough of the Giants game.

I’ve been looking into RedZone a bit; it’s interesting. It seems to be quite popular. I’d been aware of it previously, but have never watched it or really learned anything about it. There’s been some concern about what will happen to it after the NFL/ESPN deal goes through (assuming it does). That shouldn’t affect anything this season; it should be at least a year before that’s finalized.

Meanwhile, I’ve watched a lot of Phillies baseball this week. I’ve just been in the mood for baseball instead of, really, anything else. They’ve lost their last three games, so that’s disappointing, but I still like watching them.

Streaming Chaos

Preseason football has started up, so that’s got me thinking about how I might be watching (or not watching) football this year. Last year, I had YouTube TV, and the year before that, I still had the broadcast basic package from my cable company. So this is the first time I won’t have any way to watch regular old broadcast TV during football season. (I could still break down and re-subscribe to YouTube TV, but I’m not planning on doing that.)

Streaming is getting even more complicated this year, it seems. Here’s a fun article about how to watch football this year. ESPN has a new streaming service starting up soon. If I understand things correctly, my ESPN+ sub will become an ESPN Select sub, so no big change there. I guess I could switch to the “full” ESPN service, and then I’d be able to watch… whatever games are on ESPN/ABC but not ESPN+. I’m honestly not sure what those will be. Monday Night Football might be ESPN/ABC only, or might also be on ESPN+. Who knows?

For Sunday night games, I should be OK. I still have a Peacock subscription. I don’t have any way to watch Sunday day games right now though. I canceled my Paramount+ sub, so no CBS games. Fox has a new streaming service starting up, which should carry their Sunday games, but that service also includes Fox News, and I’m dead set against supporting that stuff, so I guess I’m going to go without.

I did just pay for a year of NFL+ Premium. That gives me NFL Network and NFL RedZone, so that’s something. I’ve never actually had RedZone before; maybe I can just watch that on Sunday? The NFL+ sub should let me watch all the Giants games on my iPhone or iPad, I think, just not on TV. So maybe I’ll just watch football on my iPad from now on.

Here’s an interesting article on the new ESPN/NFL “mega-deal.” I’m not sure I even understand what’s going on with football right now.

And, of course, I could just give up on football. I’ve done it before. I’ve gone back and forth on it, over the last decade. Some years, I’m enthusiastic about it, and some years I’m not. (Often, that has to do with how well the Giants are doing that year…)

Meanwhile, I’m still enjoying baseball. I watch the Phillies on MLB.TV a few times a week. I’m always a little annoyed if a game is blacked out because they’re playing the Mets (or Yankees), or because it’s on ESPN or wherever. But there are so many games in a baseball season, it doesn’t bother me that much if I miss a few.

Of course, if the Phillies get into the post-season, that becomes a problem, as those games aren’t on MLB.TV. Sigh.

Frustration

I have a bunch of stuff on my mind, and a few topics for blog posts I want to write. But I’m going to start with a little decompression about my work week. (I should first say that I need to be careful about this, since our policy on blogging about work has been tightened up recently. But none of this will come anywhere near to violating it, I think.)

We’re working on an upgrade to our AX environment right now, and we started some testing in a new test environment this sprint. This includes (for me) getting some web services working on the new test server, and getting them to point at the new AX test env. So a lot of my time this week has been spent whacking away at web services with a hammer, trying to get them to work. That’s always frustrating. It always seems like I need to try six different things until I finally hit on the one that actually fixes the issue. And I always feel like an idiot for not being able to get there faster.

I’ve been thinking about why this kind of work is frustrating, and I think a big part of it is having no clue how long it’s going to take, or how close you are to solving it. With certain kinds of work, you can break a problem down into parts, and work through them, so you know when you’re 10% done, or 30% done, or 80% done. But with this kind of troubleshooting, you don’t know if you’re going to need to try 5 things or 10 things or 20 things before you find the right thing. And you don’t always know if there’s one thing wrong, or two things, or ten things.

I won’t get into details on the actual issues I hit, but I will say that one of them was basically a new permutation of this issue I hit back in 2011, so it was fun to see that again! And another one was related to the topic of this post from 2020.

I’ve been using AI tools to help me with this work, and I’m not sure if they’re any more useful than just plain old internet searching. Sometimes it seems like they are; I can get a lot of seemingly-useful ideas from a chat with Copilot. But then the real answer comes from a simple search that leads to a Stack Overflow question/answer, or a GitHub issue. (For instance, one big problem I had this week was solved by reading through this GitHub issue from Microsoft’s WCF repo.)

My big project for this afternoon was working on a side-project for a little competition we’re having at work. (It’s one of those things where small project teams propose something, do a little work on it, then present it to the CIO. And then I guess the winning project actually gets green-lit.) That project is turning out to be a bit frustrating too. (It was supposed to be a nice break from the frustrating stuff!) First, I needed to get myself set up under our corporate developer account with one of the big package carriers, which we only managed to get done yesterday. And I’m still not completely set up, to where I can do what I actually need to do. But I can start testing, so I started work on that.

The project involves using the carrier’s webhook API for package tracking. My idea was to start out with a simple Azure function that I could point the webhook at. Then, to start, I’d just log the info I got from the carrier. The next step would be to hook that Azure function up to some kind of queue in Azure. Then, after that, writing another Azure function that would pick stuff out of the queue and send out notification emails. Basically, I was going to put my AZ-204 skills to work on a real project! (Well, not entirely real, but a POC at least.)

It took me the whole afternoon to get a simple Azure Function set up. I started out trying to use Copilot chat with GPT-5, which they rolled out yesterday, to help me out. That looked really impressive, showing me status info about what it was doing, and generating a lot of text with pretty specific instructions. But it seemed to be giving me quantity over quality. I turned GPT-5 off, and then managed to get a lot farther.

My initial idea was to just enter the C# code for the function directly in the Azure portal, but I set it up in isolated mode, which apparently doesn’t let you edit code directly in the portal. So then I tried using Visual Studio Code, which is supposed to be an easy way to quickly develop and deploy Azure Functions. That led me down a path of installing a bunch of stuff locally. I was initially doing this on my laptop, so I had to install .NET SDK 8, plus a bunch of VS Code extensions. At some point, I got nervous about how much stuff I was installing on my laptop, and switched over to my regular dev VM, which is where I’m supposed to do development. So then I had to install all that stuff there too, since I’d never installed the .NET 8 SDK there, or set up VS Code for Azure dev. So I probably killed an hour just getting my environment set up.

And then, once I had everything set up, I started hitting a bunch of weird little snags with editing, compiling, and running the function. I eventually gave up, and with some help from Copilot, set up the simplest Azure Function project I could, entirely from the command line, then got it running and uploaded to Azure. So that probably took another hour, and the end result was just something that would print “Welcome to Azure Functions!” when you hit the URL for the function.

After that, I got the thing working in VS Code, and managed to change the function from a GET to a POST function. And I thought I had gotten far enough with it that I could hit it from the carrier’s test page, but all I can get back from that is an error, with no details giving me any clue what’s wrong. And that’s pretty much where I ended my week.

I don’t really drink anymore, but I think I kinda want a beer right now. Or maybe just a bowl of ice cream.

reading comics, and (maybe) done with COVID

I took my last dose of Paxlovid today, and got a negative result on a COVID test this morning, so I think I’m over COVID. (Unless the Paxlovid rebound thing hits me, like it did in 2023.) I think I’m probably OK to go over to the farmers market a little later, which will be the first time I’ve mingled with other people in a week. We’ll see how that goes.

Meanwhile, I read a lot of comics this week. I didn’t have enough energy, initially, to read prose, so I stuck with comics. Then, I got on a kick, and kept going. I read a really random assortment of stuff, mostly from old Humble bundles, but from other sources as well.

Here’s a list of most of the stuff I read:

  • American Born Chinese by Gene Luen Yang
  • Superman: Earth One, Vol. 1-3 (JMS)
  • Vampirella Masters Series Vol. 4: Visionaries
  • Mind the Gap, vol 1-3
  • Angel Omnibus
  • Alex + Ada: The Complete Collection
  • C.O.W.L. Vol. 1
  • Detective Comics 471-476 (Englehart/Rogers)
  • Velvet, Vol. 1-3 (Brubaker/Epting)

All of it was quite good.

I also just bought yet another Humble bundle, this one containing a bunch of stuff from James Tynion IV. Most of the stuff in the bundle is DRM-free PDFs, but there are a couple of oddball items in it.

One book is redeemable only through DSTLRY, which is a company I’d heard of before, but hadn’t really investigated. And another two are redeemable through Neon Ichiban, which I hadn’t heard of, and isn’t live yet. They seem to be related to each other, and are both founded by a couple of ex-Comixology guys. I guess DSTLRY is more of a “publisher” and Neon Ichiban is more of “platform”. Here’s an article from Comics Beat about Neon Ichiban. So now I’ve signed up for a DSTLRY account, and put myself on the Neon Ichiban waitlist, though I’m not really enthusiastic about jumping on any new bandwagons.

Right now, I read all of my DRM-free books with Panels, which has evolved into a really nice app, and seems to be under continued active development. I read all of my Comixology books with the Kindle app, of course. And that’s about it.

I did also use the Comics Plus app this past week to read a book. That app is tied to my library card, and lets you read a fairly impressive catalog of comics, for free. I’m not really sure how the licensing works, but it’s different from Overdrive/Libby. With Overdrive, your library “owns” a set number of digital copies of a book, and you may have to get on a waitlist before you can read something. With Comics Plus, there are no limits. If it’s in their catalog, you can read it. So that’s great. Unfortunately, the user interface for the app is pretty bad. It froze up on me a number of times, and I couldn’t move from page to page without force quitting and going back in. And it doesn’t have good functionality for zooming in, which is something I need.

Somewhere along the line this week, I also started looking at Global Comix, which has been around for a couple of years. I’m pretty sure I’d heard of it before, but hadn’t looked into it. Here’s an article on them from Comics Beat. I’m definitely leery of getting too involved with any digital comics platform other than Amazon/Comixology, as it doesn’t seem like any of them are likely to be around for the long term. I notice that Omnibus shut down last year. They only lasted a year or two, so I’m glad I didn’t get too involved with them. And of course Dark Horse Digital shutting down was a big pain for me.

Well, regardless of all that, I have quite a lot of comics to read. Certainly enough, at this point, that I won’t run out before I die, even if I don’t ever buy any more. It’s interesting (if a little morbid) to start thinking about things from that perspective.

Well, that’s probably enough pointless rumination for today. Here’s hoping I have a nice COVID-free week.

COVID again

I felt like I was getting a cold last weekend, on Saturday. It got worse on Sunday. Long story short, I got COVID again. I took off from work Monday through Thursday. I started Paxlovid on Tuesday. I went back to work today (Friday), working from home. I’m feeling a bit better, but very tired.

My last bout of COVID was in 2023. I’m hoping this one is pretty much done now. I’ll be taking the Paxlovid until Sunday, then I hope I’ll be all better. I’d like to have a “normal” week at work next week. I’ll test myself again on Sunday or Monday. If I’m still positive, then I’ll try to at least work from home next week.

I’m fairly exhausted right now. I had to stay up for an after-hours deployment today, which is now done. So I can go to bed. Of course, it’s Friday night in Somerville, so Main St. is pretty noisy. Maybe I’ll try to watch the rest of the Phillies game before bed.