And Then...

[davidklecha]

Dave just did something really stupid.

And I'm going to pay for it by calling one of our clients at 0630 when they get into work tomorrow and walk them through the fix.

Sometimes, I'm dumb. Especially around 10 at night.

Comments

[queenoftheskies.livejournal.com]

It's really hard to be bright at 10:00 at night.

I hope whatever happened isn't too much of a problem for you.

[daveamongus.livejournal.com]

Pretty much.

Turned out okay, as it happened. Got ahold of someone before they got going full steam today.

[pnkrokhockeymom.livejournal.com]

Today, after many, many days without one off and after many, many days of this stupid flu, I filed the wrong brief with the Court. There were two versions of said brief, one edited, one not, and I printed up the wrong one, signed it, and sent it off to the Oakland County Circuit Court. I didn't even notice until supervising partner came in and said, jokingly (thank goodness he's a nice guy), "So we didn't file the brief with my changes, eh?" Me=mortified.

Sometimes, we're all dumb. Hopefully your fix isn't too difficult.

[rudius-maximus.livejournal.com]

That's ok. After doing professional IT work for so long, you're bound to pull a boner once in awhile. My two favorites:

1. About 6 months after graduating GVSU and working my first job, I updated the sales VP's laptop with the wrong BIOS and cooked it. Killed the laptop stone dead.

2. At my current job, after only having been here around a year, I did the exact same thing. Except this time, it was on a RAID controller that managed the drives to the manufacturing server. At the time, this server did everything from housing the manufacturing system (everything from sales orders to shipments), e-mail, file server, etc... my boss came in, along with our EDI consultant, and we worked on it until 5:30am. This happened in 1999, and thankfully was the last major F-up I ever did at this place. Two promotions later, I'm still here, though my boss still brings it up when he's giving me shit.

So, yeah. "Leaving well enough alone" is a mantra I learned the hard way. Twice.

[daveamongus.livejournal.com]

Heh. Nice.

Myself, I was remoting into a client's server so I could perform an automated rebuild on their database, then reboot the server. Only, one other workstation in the office was on, and the software open on it, so the rebuild utility wouldn't run. Without remote access to the offending workstation, I couldn't kill the program, so I to figure out how to just isolate it.

When that failed I had the bright idea of isolating the server. By disabling its LAN connection.

Oops.

[rudius-maximus.livejournal.com]

I remote desktop into my home machine every day to check e-mail, Quicken, etc., and have done variations of this before. It usually involves dicking around with my router's configuration.