Losing Steam
First dog watch, 1 bell (4:56 pm)

This has been an exhausting week. Computer troubles galore, there must be something in the air. The past two days I've woken up with a sore throat, possibly due to all the stress I've been under.

Last night a change I was ultimately responsible for broke our software for about three hours. The change wasn't my fault, but I still should have caught it. A #define directive was renamed in our main code branch and integrated to my "utilities" directory. When I recompiled the server-side code, there was a problem which should have clued me in to the bigger problem hiding behind it.

Anyway, there were a lot of failures in processes along the way. I think the biggest problem is that nobody knows the "whole picture" of this project.

But we learned a good lesson, and the impact (from a bigger perspective) wasn't nearly as bad as it could have been.

On top of all this, we've had computers crash. One, on Monday, just stopped working. The motherboard, power supply, CPU, and hard drives were all dead. We basically had to replace the whole thing. Another video card (just this morning) literally blew up. Three of the capacitors just exploded in the case! A UPS had a melt-down and blew the power supply out of another machine at one of our remote locations.

I tell you, there is something in the air. Back up your data if you don't already. Really, go do it right now.

Leave a Comment »

Leave a Reply