Phil Parkin wrote:
Thom A wrote:
Don't you just love it when you get a "urgent" work request that needs to be done "NOW", because it's impacting staff productivity, so you get the work done in dev and test it (all works), up scale it to UAT and advise it's ready for testing within a day; because it's "urgent".
Then, one month later, as you're working through out standing commits, you stumble across this "urgent" work that's still not in Live and think "Ooops, maybe i missed the feedback." So you send an email across, double checking that testing was completed and successful, and apologise that it hadn't been deployed yet, to get the response "Oh, we weren't planning to look at that until January".
Was it really that urgent you had to escalate the issue to the directors that you wanted it fixed "NOW" if you aren't going to even look at the build for 3 months?! Argh. >_<
One good thing about this is the amount of ammo now in your possession when the next 'urgent' request comes up!
Nah... always do "urgent" requests quickly. They're almost never urgent and will frequently end up like the one did for Thom but you can really gain the upper hand on these types of things. First, if they really are urgent, you are a hero. If they end up like Thom's, then it's already done, there's no chance of you failing to hit the deadline, and you know what to expect for deadlines in the future when it comes to people wanting to make changes because they didn't actually know what the hell it is they actually need but knew something had to be done even if it was wrong and you still end up the hero but, sometimes, with apologies from the idiots that were urgent. 😀
Remember... it doesn't matter if something is urgent or not... we get paid the same no matter what. If we can look good doing it and solve people's urgencies quickly, that might help us on our next annual review and help us get a pay raise. If nothing else, keep a list of such urgencies because, on a pick'n'choose basis, they can look damned good on a resume. 😀
I do STRONGLY agree that urgencies should not turn your job into regular 60-80 hour work weeks.
And remember, practice NVO... No Verbal Orders, especially for urgencies. If you have a ticketing system, make damned sure it's used for such things. If you don't, make sure there's an email chain that you save. People with urgencies are also the first to look for scape-goats when THEY fail to urgently perform on their own urgency. It's a shame that things turn out that way but they almost always do.
I've also found that if you get people to write their "gotta have it NOWs" in the form of a ticket or an "official email", a lot of urgencies simply vanish or the real truth about them being needed in several months suddenly appears.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)