Log in

No account? Create an account
23 March 2005 @ 03:37 pm
One Blessing -- Hold The Disguise  
Earlier today I had been nervous about the job situation. I've got two weeks and then I have no more income. Not a really fun place to be.

Then I came back in from lunch. I mentioned to a couple of users that I'm almost finished with the current change I'm making and that it would be good to get that program, along with the other change that I made, installed to production before I leave in two weeks. (Never mind that next week is month's end, and we don't do roll-outs there -- have fun! *parade wave*)

This sparked off an amazing chain of "what change? I didn't know about any change. Did someone authorize this change? Shouldn't someone authorize this change? This isn't a change we requested. Why are we doing this change again?"

At the end of it all I was feeling much, much happier about leaving this job.

Interview rescheduled for Tuesday. And I'm going to have to call (as opposed to send e-mail) to the company that I interviewed with earlier in the month. If they aren't going to hire me then I at least deserve the courtesy of a phone call telling me that, dammit. If they haven't decided yet, then it also wouldn't kill them to tell me that as well.
kazuhiko04kazuhiko04 on March 24th, 2005 04:14 am (UTC)
Just as a matter of interest, are you having to deal with all this Sorban-Oxley (spelt something like that) rubbish?

We're having so much red tape tied around as where I work that it looks like Christmas. Every change is supposed to be signed off by three people to be implemented, then again after testing, then again for migration to the live system... >.
Sandpanthersandpanther on March 24th, 2005 04:05 pm (UTC)
Yep. My department attempts to ignore it, since it smacks of good business procedure. The higher ups (who now are responsible for their underlings being imbeciles) smack my department and mutter dire warnings about the consequences if we don't comply. I am amused, watching things that I have been saying for some time need to be implemented suddenly turning into a top priority.

For companies with a clue, SOX is a pain in the butt. OTOH, my department has had a tradition of slapping in changes without any warning, testing, or documentation. So for them, SOX is a good thing. Mind you, I'm probably enjoying the SOX regulations more than most since now everyone is starting to get a clue as to what I've already been having to deal with because my systems must comply with FDA Part 11 requirements -- many of which overlap with SOX. So now I have big-wigs shoving process and procedure down the throats of people I used to reguarly get into heated arguements with over how to install software. ("No, we can't just install it without telling the users. No, we can't install it without &^%# well testing it. No, we cannot go tell the FDA to go f--- themselves!! (Well, I suppose we could, but I don't think anyone would like the consequences.)")

(Yes, someone did really propose the way to deal with FDA regulations is to tell them to go f--- themselves. This is the same man who I commented on last week who was complaining about vulgarity in the media. There are reasons I think this man is an idiot, and I did the happy dance the day he left the company.)