Yesterday was a beating...

So, Monday at work. And by 8:07 I knew it was going to be a particularly Monday sort of Monday because somebody called up to drop a major technical problem in my lap while I was in the midst of trying to deal with a completely different major technical problem that's been going on for a week now. (And that's not to mention the three other major technical projects that I'm trying to get back to!) 

So the new issue tied up the morning, and after all that the best solution is to move the whole thing to a new setup -- a project which we'd originally scheduled for March/April of 2019. It's now rescheduled for next week, and we've slapped a bandage on the existing setup to hold us until then. 

The second issue then ate most of the afternoon; it's a system that keeps kicking everybody off when the IIS service crashes, but there's no indication of why it suddenly started crashing a week before last Friday. We've tried a couple of things, but at this point they're more "throwing darts at the wall and hoping something hits" than actual troubleshooting. And, of course, it's erratic -- which makes it even harder to pin down. I'm hoping that the stuff we did yesterday will help, but it's immensely frustrating to have the system start breaking like this when we haven't changed anything. 

And then a particular document that I was supposed to post on the website came in at the very end of the day (not unusual in itself) at 760 MB (a quarter of a gigabyte, and perfectly ridiculous). So I didn't leave work until an hour after my day was supposed to end. 

I went to bed early, obviously. By the time I got the boys down, I had nothing left. Even reading was too much for me. 

But, I've gotten a good night's sleep and a decent breakfast; here's hoping today goes much better.