Like a lot of people, I’ve become addicted to Wordle, the word guessing game first created by Josh Wardle. It’s sort of like Mastermind for words — you have to guess a five letter word in as few tries as possible. It does not give you any meaning based clues; instead, you enter a guess, and it colors any letters that are correctly in the right position green, any letters that are in the word but in the wrong position a mustard yellow, and any wrong letters dark grey. There’s only one puzzle per day. The game makes it easy to share your score via text or social media by placing an obfuscated version of your guess on the clipboard:

Wordle 679 4/6

⬜⬜🟨⬜🟨
⬜🟩🟨🟨🟨
🟨🟩⬜🟩🟩
🟩🟩🟩🟩🟩

(I probably should have gotten that one sooner)

My sister Karen also likes to play, and we tend to text each other our scores. I think we’re basically in the same league; some days she does better than me, somedays I do better than her, and somedays we do the same.

Wardle originally created the game for his wife, and when it became popular, he sold it to the New York Times in January 2022. The Times has maintained free access to the game.

One of the things they’ve added is Wordlebot, which provides an online analysis of the way you played today’s puzzle. What I find fascinating about Wordlebot is the way it solves the puzzle. It’s appears to be mostly probabilistic.

Here’s the way it appears to solve the puzzle:

• It starts off with a fixed list of around 3000 words
• It makes an initial guess, usually SLATE, and then filters out those words that the clue response eliminates. When analyzing your score, it will tell you how many words are still possible based on your guesses.
• It makes another guess, based on the words remaining, probably weighted by some sort of word usage, and repeats until it gets the word.

I don’t work that way. For one thing, even though I have a very large vocabulary, I don’t keep all of them in my head. Here’s I I solve it:

• I start with a word with a couple of vowels and some of the more common consonants. For a long time it was HEART, now I tend to follow Wordlebot and use SLATE
• If none of the vowels hit, I’ll go with a word like SOUND to test a couple of the other vowels. If I did get a vowel, I then have to consider its placement, how many of them I got. Many five letter words have two vowels; if I only got one, then it’s not unlikely there’s a second, and I’ll choose a word to test that. I don’t play in hard mode,
• If one of the vowels is in third position, I tend to try out two letter consonant combinations, since words that begin with a consonant tend to be more common than words that begin with vowels. If I know the first or second letter, that can be constraining, since a lot of letter combinations don’t work — think, for example, “dv”. If I can’t find a two letter consonant combination, then I’ll try a vowel in first position.

In general, I have a sense of English letter patterns, but what I don’t have is a sense of what words I have not yet eliminated. I can’t tell you how many times I’ll agonize over finding a word that fits, trying out different letters to see if they sound right, and then finally, I’ll trip over the word, and it will be immediately obvious it is right.

Then I’ll look at Wordlebot, and it will tell me I’ve eliminated all but one word, and I should have it in the next turn. If I’ve done well, it will have be on the next turn, and other times… not.

I’ve been a Verizon FiOS for the past fifteen years. Up until last week, I was a happy Verizon customer for TV, internet and phone.

I arrived home last Monday to find that the internet was down. A quick check showed me that the TV was down too.  I didn’t bother checking the phone — I seldom use the house phone anymore — but I assume it was down too.

The first thing I did was go downstairs, and check the Optical Network Terminal (ONT). I saw no indicator lights on it. 

The next thing I did was use the Verizon FiOS app to try to contact support. Oh, gawd. It. was. so. bad. Slow, laggy, and the user experience sucked. I build user interfaces for a living, and one of the the things you learn is that when the user acts, your app needs to react.

This app lead me through a series of yes/no questions, and when I answered each one, it sat there. No reaction whatsoever for seconds. The buttons didn’t highlight to indicate they’d activated, there  was no focus ring to indicate that the button had been clicked, there wasn’t any kind of spinner or progress bar to indicate a request had been sent to the server and that the app was waiting for a response. It just sat there, and I wasn’t even sure it hadn’t died. It finally led me through a series of checks which seemed to indicate that it was testing the ONT to see if it had power, and when it got the the last screen…. it was empty. Nada.

Having gotten nowhere with the in-app diagnostics that were supposed to get me back up and running “in just a few minutes”, I used the option to get a call from Verizon. I gave them my cell phone number, and sure enough, I got a call in just a moment. It went downhill from there. Press one for this, press two for that, etc, for a long chain of options. Finally it agreed that I could talk to a representative. And then it put me on hold for about ten minutes (it felt like an hour, but I just checked my phone). I finally got to an operator who told me that it was a known issue that should be fixed by 7 the next day.

So much for Monday night. I’d spent about an hour between the app and waiting on hold. I had no TV and not much internet — just cellular on the phone — so I actually read a book.

The next day, Tuesday, I got up early, because I knew that with the internet down, I would have to go into the office to get work done. Sure enough, the system was still down, so I went into Watertown. 

When I got back, the system was still down, so I called Verizon back; and this time I pressed a little. I got another operator, who continued to tell me that the problem was a cut fiber somewhere. I told him I was standing in front of the ONT, and it had no power. No, no he assured me. The problem was on their end. Well, what if there is a problem here too, and you fix your network problem, and I’m still down? Didn’t listen, just said they were working on it, and he would check in at 10 PM to see if I was back up. He didn’t and I wasn’t. I was beyond furious at this point.

The next day was Wednesday, the day we ordinarily go into the office, and I had a decision to make. Should I go in, or did I need to stick around to see if a tech would come?

I called Verizon back, and promptly got dumped into a robosystem that swiftly informed me that I already had a ticket open and it would not be resolved until 8 PM, and that there was nothing else anybody could tell me. Click.

By this point, I was pretty damned sure that the problem was sitting in front of me. They’d sent me a mail last year saying it was no longer supported, but since I work from home, it’s hard to be both available for a tech and get work done. So I put it off. But I know that indicator lights mean something, and if even the power light is off, there’s a problem. I was boiling mad, so I tried using the “I want a call” option again, and this time, I got an operator who listened.

He scheduled a tech to visit that day to diagnose the problem, and another tech the next day to upgrade the system. Finally. I mean, I wasn’t thrilled that I’d be down for two days, but at least, I was confident that the problem would be solved. I was hoping the tech could get the existing system back up so I could limp along for a couple of hours, until I had to go down again the next day for the upgrade, so I texted my boss to let him know I wouldn’t be available today and part of the next day.

James, the technician who came that day, was awesome. He took one look at the old ONT, pronounced it dead, and told me he could replace the ONT and router and arrange with one of his co-workers to come in and complete the upgrade that day. And he did. He got the internet back up in a couple of hours, running at much higher speed, and his colleague came by around 4:45 to handle the TV upgrades. It was done, and I now have a much better system (aside from the fact that the wifi doesn’t reach well into the bathroom). James and his colleague (and I wish I could remember her name) were the heroes of this little misadventure.

This whole thing feels like such an unforced error. As I said, up until last week, I’d been a very enthusiastic Verizon customer, because the previous times I’d called them, they’d responded quickly and well. I would get advertisements for other ISPs and chuck them, because their service is notoriously bad, and why would I want to deal with that when I was dealing with a good outfit that took customer service seriously?

At least, I was.

They burned so much good will with me over the course of about forty hours. Clearly, some bean counters somewhere realized it was cheaper to get rid of a bunch of representatives who knew what they were doing, and replace them with a poorly made app (which is clearly just a series of web views) a shoddy, unresponsive back-end backing it up, and outsourced customer service operators working off canned scripts that try to avoid having to send out repair people.

Yes, it’s cheaper. But it’s not more efficient.

It takes a hell of a lot of money to attract a new customer. I remember when I first got FiOS reading that they were spending ridiculous amounts of money on each new customer. If they can retain existing customers, that’s money they can amortize, not spend again trying to replace that customer. Furthermore, if they can keep those customers happy, they’ll tell other people, and hopefully that means attracting new customers is easier and less expensive.

Instead, they’ve chosen to become just as customer-hostile as the other guys. What a goal to shoot for. Instead of diagnosing the problem properly the first night, and sending someone out the next day to deal with it — since the problem started in the early evening, I would have been content with next day service — they fumbled for about 36 hours, while I became more and more enraged.

And I’m damned well making sure everyone I come into contact with knows about it.