Our site goes beta in 36 hours. I'm wavering between thinking it's ready for prime time and wondering what the fuck we think we're doing putting it out for public use. I know that a dozen of me couldn't find all of the bugs in the system, but I still feel bad when somebody besides me finds one, especially if it's serious.
I love this last-minute crunch, when everybody is scrambling to get things done and pushing as hard as they can to make the launch successful. It's been nearly five years since I was in a tiny little company that was trying to prove itself, and I've really missed it.
One of our developers is extremely good, and the other one keeps telling me things are fixed when they're really only half-fixed. For example, there's a page where you can create a particular type of thing, and another one where you can edit an existing thing. (There are good reasons for them being separate.) There was a bug that caused a relatively minor but ugly problem with the create page, and that bug was reported by somebody other than me.. When I looked at the bug report, it was immediately obvious to me that the same bug would exist on the change page. It did, and the developer only fixed it on the create page. I get really tired of bouncing bugs back to him for more fixing.
We're interviewing director of operations candidates at the rate of one per day. It's a tough role to fill, becaues we need someone who can come in and immediately be the sysadmin and the DBA and the network engineer, as well as being the operatins architect and growing the department when it comes time to do so. The peopole we're finding are either very senior people who haven't gotten bits under their fingernails in ages, or they just aren't smart enough to do the whole job. The only person we've interviewed so far who would be completely suitable is my old boss from Post.
I'm a tough interviewer. I start off by informing them that while i'm the QA geek now, I've been director of operations in a past life, and that when I was I could do the job of almost everyone who reported to me. I guess that's actually kinder than just letting them think I'm a typical technical-lightweight QA person, but I think it scared at least one person.
I also ask nasty questions that ask them to troubleshoot a very difficult problem. They wind up trying to guess what the problem is, and all I want to hear is that they listen to the clues well enough to figure out that it's an application issue, and then give me some suggestion of how they might troubleshoot the application.
One guy kept insisting it had to be a network problem even though every clue I gave him pointed to something else.