Yesterday was a really strange day, for several reasons. Firstly I opted to take the day off since the week as a whole had been one of the worst in a very long time. The summary can be that the project from hell… went to hell. During the course of the last two years, it has been common place that the vendor has invented new requirements on a regular basis. For example in a meeting on Wednesday they produced a network diagram of how the system should be designed… that would have been nice to see roughly two years ago when the project started. As a result it was once again up to us to save the day and try desperately to make things function. Over the course of 45 minutes I threw up a brand new reverse proxy server and configured a dozen or so redirects to get things functional again. It was all for naught however… because even with things configured their application was still failing to function at an acceptable level. So as a result the big launch was scrapped and we are now trying to regroup and decide when exactly the vendor application is working well enough to try this again. Essentially I know exactly how the Healthcare.gov team felt when vendors failed to provide a fully functional product.
Yesterday was supposed to be a chill day that I stayed at home, worked a little bit… and overall relaxed but that was not apparently in the cards. I woke up to find my cellphone locked beyond reason. I pulled the battery and it began a pattern of locking up after 10-15 minutes of usage. I tried uninstalling everything that was not critical, but the error message I kept getting was that TouchWiz was failing, that being the default shell of Samsung phones. I tried booting into recovery mode and clearing the application cache, and eventually I was left with only the thermonuclear option of resetting to factory settings. So I hurriedly started shifting all of my authenticators to running off of another device, and in several spurts of pulling the battery to reset the device I managed to use it long enough to do that. I held my breath, and hit the button resetting the device…. which actually took far less time than I would have thought. The thing is… all of the important stuff on the device other than the applications gets backed up to google drive, and all of my pictures to the google photos site. In theory I didn’t lose anything, and the moment I logged into my google account it started downloading everything that I had on my device before and restoring the application states. In any case… resetting a phone is not something I would want to do often because it caused more anxiety than just about anything I have done period. There are basically three devices that need to function for me to be happy… my phone, my laptop, and my gaming machine.
The other major problem of the day was our primary cable box. We have the in home networking thing where all of the cable boxes are supposed to talk to each other, allowing us to record programs and watch content from the DVR from any room with a box. This has not always worked as intended, but lately it just hasn’t worked at all. The first symptoms were that we could no longer access the DVR remotely, then could no longer schedule something to record. There have been a few situations where the box itself did not come up cleanly after a power spike… and I had to hard reboot it a few times. Yesterday I attempted another one of these reboots hoping to clear up the problems, and what I got instead was a dead box. I am extremely lucky in that I have a friend that I have known for years, that is a developer for the cable company. So with his help we tried a bunch of different things to troubleshoot the problem. The behavior that was happening is that after a hard boot it would throw two error codes Er:54 and Er:55 then start counting from H0:01 to H8:00 ish, and repeat that over and over forever. This happened once before and I let it sit like this for an entire day and it never recovered on its own.
Essentially what this is a sign of if you ever see this on your own cable box is that apparently it is trying desperately to dial back home. The H001-H800 is it cycling through frequencies from 1 mhz to 800 mhz trying to find a channel to communicate on. It has to dial home for it to be able to do a health check and make sure that the software is up to date. So until it finds a signal it won’t actually boot into the cable box software. Now on the cable side my box was showing as being a “non-responder” so for whatever reason, the communication framework inside the box was unable to talk… and essentially the box itself was dead. I unhooked the box and brought it to the local office, roughly a mile from the house and I have to say I am super impressed. They scanned the barcode on the back of the unit and walked into the back and handed me a new one with really no questions asked. Took it home, hooked it up… and at first I was only seeing the standard definition channels. I had to call into the main office and they sent some signal to my box that caused a reboot and after that everything was back to normal. I guess the box had been dying for awhile, because everything is much more responsive on this one with relatively no menu lag. I seriously think I am one of the few people in the country who actually loves my cable company, because I have had almost nothing but good experiences with them. At the very least I have had nothing like the horror stories I have heard about Charter, Comcast or Time Warner.
The focus of yesterday however was that Diablo 3 Season 5 started at 5pm pst, and that was pretty much the only thing on my mind all day long. I am not sure what it is about Diablo season play, but it makes the entire experience more enjoyable for me. It gives us all a reason to start from scratch and re-experience all of the aspects of gearing up and learning everything all over again. There were a few hiccups at the beginning of the evening, right around the official launch time… but I assume those were all related to server load. I was able to use the new Rebirth function on my Crusader, but I had to log out and back in for it to take. Once we all managed to get in game four of us started a group and spend the majority of the evening rolling around together in a glorious murderball. At some point Ashgar dropped out and a little bit later Mor did was well, which ended up changing the group comp to include Carthuun and Grace’s “Precious”… otherwise known as the Kraken by the AggroChat folks. It was awesome to get to meet him and have him on voice with us.
We spent the majority of the night doing bounties and quite honestly that feels like the fastest way to level. We started playing at 7 pm my time… and I finally tagged out of the group around 10:30 and in that amount of time minus a few breaks I pushed from level 1 to 55ish. Today once I wrap this blog post up I will be back to working on my Crusader, and trying to decide what abilities I actually want to use. The problem with running around with three Wizards is that I always feel like I am way too slow to keep up. As a result I had to generally focus on movement abilities to try and keep ahead of them. Towards the end of our play session I started focusing on the few ranged abilities that the Crusader has, but regardless of what I do there will be no way I can really compete with the sort of damage that disintegrate throws out. The other side effect of my build is that I am focusing on some of the crowd control effects that I have like the flail whip that stuns, and judgement that is a big targeted AOE stun effect. The idea is that I am trying desperately to “tank” the stuff while the wizards burn it to death. I think the thing I like the most about Diablo seasons is that we hit it hard and heavy for a few weeks, and feel like we accomplished something… only to move on to other things until the next season comes along. It gives me the feeling of a new MMO launch, over and over… which for me really is the best part of an new MMO. That moment when all of your friends are super focused on the exact same thing for a period of time.