This morning I thought back to the time I launched a commercial, consumer-facing web site back in 2000. It didn’t go smoothly for a number of reasons. Most of the reasons were my fault, but it didn’t help that we had a customer that put us under unbelievable time pressure that we should have pushed back against. We didn’t have time to do adequate QA on the site, particularly when it was under load, so the site worked well when four people were using it, but collapsed utterly when the customer subjected their entire user base to it at once. D’oh.
This actually turned out to be not a huge deal in retrospect because the business was doomed anyway (we were marketing our products and services to a bunch of customers who were destined to mostly go out of business within months). But obviously, this is not how you prefer things to go.
When I posted on the Approver.com product blog last night that I loved launching products, I should have mentioned that I loved doing it as a product manager and business owner, not as a system administrator. As a system administrator, I hate it. Some developers hate dealing with customers, some hate compromising with the suits on what’s going into the 3.1 release. System administration is the thing that I absolutely despise.
I was thinking about this today because I woke up this morning to see that Approver.com was unresponsive after Om Malik linked to it last night. I shut out everything in my brain until I could get to my Mac and log in to the production server to see what was going on.
So I’m sitting on my bed at 7AM this morning in my shorts with my Mac on my lap, remotely poking the production server and muttering things like "hmm, you seem pretty perky to me, why aren’t you serving up data?" while in the back of my mind I’m wondering whether I’m going to be able to get my kid off to kindergarten that day.
When I can’t figure out what’s going on in four seconds or less, I think, oh crap, it’s 2000 all over again. Except…it isn’t 2000 all over again. I have six years of experience under my belt that I didn’t have then (and for an essentially self-taught coder with no computer science degree, that makes a huge difference).
A while back ninja sysadmin Martin Kelly dispensed some pertinent advice: the first task a sysadmin should perform when faced with a crisis is to go outside and have a cigarette. Unfortunately, this morning I had no cigarettes and haven’t ever smoked one, so rather than adding a new learning task to my plate, I had a brief conversation with my four month old assistant sysadmin. He gave me a big smile which made me realize that everything was going to be OK, and then I went down and fixed the problem in like five minutes.
The problem was something related to configuration I’d done a long time
ago, but fortunately due to some other good decisions I made when I first started coding Approver.com
(mostly having to do with basic stuff like logging and code generation
tools), I was able to resolve the error about 10 minutes after I woke
up. (So…problem averted, and if you haven’t tried out Approver yet, now’s the time.)