A dark cloud descends on the office as I enter the center of operations, also known as my second home for the last thirty days. It’s late morning, sometime between ten and eleven a.m.. Outside it’s rained for three days straight and there is zero chance of any sunshine in our near to distant future. Before I’m even able to set my coffee down on my desk, I know something is terribly wrong.

For the last week, I have been dealing with accessibility issues with our technology. Many of these issues have been focused on our clients end, seemingly the server used to host client content. On any given day I have rebooted our servers at minimum fifteen different times with little to no luck resolving any of the issues we’ve had. Dammit. God. Dammit.

Yesterday morning I learned the cause of all our issues… with the new security updates released last week, Microsoft removed/disabled the Sun Microsystems java engine in Windows. Double dammit. Our brilliant Russian CTO, in a vain attempt to rectify this problem, decides he will rebuild our client server this morning. Rebuild, without first backing up of our sql databases or any of the system modifications I’ve done over the last three weeks. This morning our server hiccups every half hour and then blue screens on us.

Version 2.0 of our software doesn’t want to play nicely with version 1.0. Databases don’t want to connect as they are designed to and our web-applications are timing out left and right. Piece of shit. What a great way to start off my day.