March 11th, 2007 — Non-Events Author: Zach
I woke up this morning and my alarm clock proudly displayed the time. I was so bummed.
I looked across the room at the digital atomic clock + thermometer on the bookcase. Perfectly correct as usual. Damn.
My last hope: the old-looking analog clock that actually has an internal Atomic radio receiver. It too, was right.
I had been so convinced that this was really going to be it. Y2K was such a huge letdown; I really thought that this time would be different. This time it wasn’t some simple 2-digit vs. 4-digit date thing. THIS was Daylight Saving Time! Something this sacred simply had to wreak havoc on our technology. How would it deal with this change? Surely my TiVo was going to record the wrong show, the power would go out, and my car would not start. Yet to my ever-living disappointment, all that happened was that my heat turned on an hour late so the house was a little cold when I got up this morning. So that’s how I began my day: coldly disappointed.
March 11th, 2007 — Events Author: Zach
Have we mentioned we work Sundays?
Well, we don’t work every Sunday, but we work whatever it takes when it comes to an event. And it just so happens it’s event time again.
Like Joe blogged, the week has been full of nearly full-time vendor-management. In addition to that full time job, we’ve also been busy trying to coordinate with our content production teams to make sure that everything was in order. And, we’ve been busy trying to make sure all of our devices, all of our services, and all monitoring and instrumentation was all buttoned up.
But now we’ve reached Terminal Velocity. There’s no stopping now. All the wheels are in motion. Between now and the end of this week, we will find out just how much our hard work and dedication will pay off. Will the site stay up? We’re pretty sure it will. Will the load balancer melt down? We don’t think so. And will we provide a killer experience for all of our users.
March 11th, 2007 — Vendors Author: Joe
Sixteen days and a few hours after a case was opened we have what appears to be a resolution to a compression problem that has been driving us insane. Our vendors senior architect worked what appears to be day and night for the past few days to patch his code and come up with a solution to a problem that was discussed earlier this week as “not possible.”
As frustrating as the experience was I am amazed at the level of commitment to resolving this issue within the time frame that we gave them. Now its time to test it out for real…..
March 11th, 2007 — Stuff Author: Joe
Last Friday as soon as Zach and I got into the office we started discussing a pile of issues we had been having with a certain unnamed network load balancing piece of hardware. Part of our frustration has been that that the vendors product is this “magic bucket of goodness” that they hold very close to their heart and we have little insight into the specific architecture of the device. This puts us at the mercy of the vendors support, and our social engineering skills, when we have a issue as nasty as the one we have been dealing with.