nolapenguin (
nolapenguin) wrote2005-12-20 10:46 am
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Aggravation. It's making me wait.
Corporate bureaucracy, two words that fill the worker bee's heart with fear. As in Office Space? Worrying about cover sheets for TPS reports would be about the mildest of worries in my workplace. When you work for a technology outsourcer, the red tape is mind boggling. It is my honest belief that MBA programs are simply mass brain-washing seminars spread over two years time, ever accompanied by the shoeboxes of cash ponied up for the privilege. Additionally, there is a direct correlation between the intensity of the mind-job and the semester tuition. Throw in some fashionably hot catch-words, like Six-Sigma or process workflow, and you've got a certified business analyst incapable of following the simplest of actual work tasks without being told to do so in concurrent emails.
Having to deal with that grief is more than a little tiresome, particularly when it's combined with the massive clusterfuck that is post-Katrina New Orleans. A guy I work with related a tale of two such purebred business leaders attempting to dine on MRE's early on in the recovery days. Considering the nature of the meals, replete with instructions that are illustrated to assist with the most unread of eaters, you should be able to average about five or ten minutes of prep time before you chow. Well ol' Standard and Poor took a full twenty minutes to open and finally understand how to eat the stuff, with one really leading the other. Pathetic.
My role in recovering from a catastrophic event was to put all the pieces back together. The primal base, workstations and network connections, are more commodity than anything, so extra help was brought in to replace destroyed workstations. After I had arrived on the site, of course. A couple of techs were brought in to the site, and lived in a rock-star posh bus. I drove to and from the site every day, three hundred twenty miles a day.
As a side note, those temporary helpers, staying at most three weeks, all got special recognition awards last week for going above and beyond the call of duty to help in the Katrina recovery. Only three, mind you, half of the temp team here, as the other half all abandoned ship or were asked to leave. No, none of the local folks, people who all had losses and were displaced from their homes, none of them were recognized. That's not sour grapes either. I wouldn't have been eligible. I'm in a different silo. I don't get awards.
So since September 8, I've been on the ground level of rebuilding a plant's IT infrastructure. I witnessed our graduation from trailer-sized generators to city power, from satellite uplinks to twin T1's, from a blown-out flooded building to a shiny new factory. My company has been supplying all the technical equipment in this rebuild. I knew, through being a part of the process, that I would get a brand new tower of glossy black servers, an ebony obelisk of humming tera-bits.
Those servers arrived a week and a half ago, two pallets grossing a half-ton. Last week they were hauled up to my server room. I directed an electrician to what I needed for power leads, what would be my attempt to start a redundant power system of my own design. I set up the rack. Then I sent out the notice I was ready to move, what were my instructions and where was my backup equipment. The answer was surprising.
"Who made the decision to put servers back down there?" asked my new boss. "Why would we put data back in there? I want those servers sent up to Norwich so [insert nameless server drone in Connecticut] can stand them up there for us."
"But," I meekly inquired of this recent effort walk-on, "these clients have special requirements. Their data access needs are relatively intensive, and a remote server would require a massive increase in bandwidth. Sir."
Okay, I didn't say sir. But I did voice my "professional" concerns about moving these servers, knowing full well in the background that the client, really the people I've work with for longer than these outsourcer idiots, would have a total shit-fit hearing that they suddenly won't have their servers in place by Christmas. My boss's objection came last Wednesday. It has taken until today to get some managers talking about the issue. My boss has still not emailed me directly, either, despite the fact I sent him the original instructions from the client's CIO to buy and set up the servers, and mapped out the before and after shots of what the server transition would look like. Translated, this schmuck had all the reason in the world to just STFU.
Instead of setting some hot Xeon servers on cruise control this week, I'm sitting around stewing and fuming while I wait for management to "come up with a plan."
Happy fucking holidays.
I thought I could get away from the bullshit, but I got to talk with my brother last night. About his work laptop going belly-up for the second time in three days, and that it must be his wireless router, and that it can't be the laptop because it's brand new, and the router is just a year old, and why would it do it when he clamped into the docking station, and it just didn't make any fucking sense. I suggested he replace the router, the third time in the past year, and just plug into the modem for now. Apparently I just "don't get it." He hung up on me.
The bad IT karma is following me.
Now, after this boring rant, I'm setting up a rack-mount UPS, minus the servers, so I can cascade the backup power for the few antiques I like to call servers.
That is all.
no subject
We had a situation at one of our remote sites where two machines were flooding the network with traffic. Dialing into the router, we found the IP of the two machines.
That site uses static IPs, so isolating the machines should have been easy. But one of the IPs was not one of the static ones, and no one was sure which machine it was. Ryan tried to look it up, but it didn't work.
I remembered a little freeware utility I once had on my work machine. I had deleted most of the freeware at my boss's command, even though some of it was quite useful, because he's got some insane beef against freeware.
But, knowing that I had a habit of putting things in multiple locations, I decided to look and see if I still had a copy of that utility somewhere. Sure enough, I did. So I ran it, and found out which machine it was. This prevented them from having to do they did last time -- shutting every machine down and watching the traffic as they came up, one at a time.
Then I made my mistake: I mentioned that I'd used freeware. I shouldn't have said that, but I didn't think about it. What did it matter, right? It was harmless, and it got the job done quickly and easily.
But my boss didn't like it. His response? He decided that I really didn't need to bring my jump drive back and forth to work every day. I only used it in my work machine, and -- per his previously issued rules -- I ran an AV check on it every day when I plugged it in. No matter. I had, to use his words, made him look like an ass, so he decided that the oft-ignored bit of policy concerning such things was going to be enforced against me.
So I got the job done in an efficient manner, but my boss didn't like the way I did it, so he decided to be petty and punish me. Great boss, ne?
no subject
Not bring a key-drive to work? Gawd, what an idiot.
no subject
There's supposedly a similar thing built into our help desk program, FootPrints, but we've never figured it out, and since we already have DameWare...
Some of the freeware I've been banned from using: Process Explorer, a much more in-depth version of the Task Manager; Autoruns, a much more in-depth version of the start tab of msconfig; and the one that I was got in trouble with the other day, some little app called Hostname.exe that, unlike the regular Hostname.exe built into the system, can give you a computer name from the IP (you run it from the DOS prompt).
He's commented in the past that I shouldn't be using Winamp to play tunes, but he's not actually banned it. Nor has he banned the external hard drives that both Ryan and I use, mainly for MP3s. I was careful to not say anything about MP3s when he said I didn't need the jump drive at work!