Slypork: Got them all right getting 8020/8200 losing points because it's timed. Yeah I'm old. Get off my lawn.

Congratulations.  I got 20 out of 20 but only scored 7720 on time.

But my nerves are shot tonight.  I had to do a database backup for one of our groups before they updated software.  The update went badly so they asked for the database to be rolled back.  I did, and that went sour, too.  Took a while to untangle and I thought I had killed a critical system, but we got it back.

Billy Liar: 20/20 Didn't realize it was timed.  What's the rush?  Do museum curators work on a speed basis or something?  Sh*t, man, take your time.

There's a switch on the start of the quiz.  You can turn off the 'timed' aspect if you want.

Slypork: Nicholas D. Wolfwood: Slypork: Got them all right getting 8020/8200 losing points because it's timed. Yeah I'm old. Get off my lawn.

Congratulations.  I got 20 out of 20 but only scored 7720 on time.

But my nerves are shot tonight.  I had to do a database backup for one of our groups before they updated software.  The update went badly so they asked for the database to be rolled back.  I did, and that went sour, too.  Took a while to untangle and I thought I had killed a critical system, but we got it back.

Ah yes. The wonderful stress free life in IT. Been in that situation more times than I care to think of. Still, you're better off than the guy who unintentionally deleted files while working to correct synchronization between the live primary database and a backup database for the FAA NOTAM system.

Oh, Christ, that poor Sod!  I really feel for him!

I hate running into a screw-up, especially if it's one I had some part in causing.  But it always helps a little if I'm the guy who manages to find the cause and fix it.

Slypork: Nicholas D. Wolfwood: Slypork: Nicholas D. Wolfwood: Slypork: Got them all right getting 8020/8200 losing points because it's timed. Yeah I'm old. Get off my lawn.

Congratulations.  I got 20 out of 20 but only scored 7720 on time.

But my nerves are shot tonight.  I had to do a database backup for one of our groups before they updated software.  The update went badly so they asked for the database to be rolled back.  I did, and that went sour, too.  Took a while to untangle and I thought I had killed a critical system, but we got it back.

Ah yes. The wonderful stress free life in IT. Been in that situation more times than I care to think of. Still, you're better off than the guy who unintentionally deleted files while working to correct synchronization between the live primary database and a backup database for the FAA NOTAM system.

Oh, Christ, that poor Sod!  I really feel for him!

I hate running into a screw-up, especially if it's one I had some part in causing.  But it always helps a little if I'm the guy who manages to find the cause and fix it.

After a customer told my manager about how helpful I had been he told me, "One 'Attaboy' makes up for three 'Oh, shiats'."

That's a better exchange rate than I usually hear.  Normally, I think it goes "One 'Aw Shiat' cancels out three 'Attaboys'".

Over the last three or four years, there have been a number of occasions where I (accidentally) damn near took out critical systems.  Some had the potential to be unrecoverable, and at least one could have resulted in *everyone* being permanently locked out.

Fortunately, I recovered from every one of these, but I'm getting too old to be part of a techno-thriller.  And I hate working on critical systems without adequate training, poor communications and coordination, and an attitude of 'Learn the systems by playing around with Production'.

Like last night's DB screw-up.  Hey, if we can't get the database back, we can revert the DB server's VM back to its last snapshot.  We might lose a week or so of data, but better than losing the whole system permanently.

...  What do you *MEAN* someone deleted all the VM snapshots without telling anyone?