Monday, April 14, 2008

weighing the option

so is it better to have a wider skillset that spans several actual job functions or just stick to my own? its such a hard question for me... i get bored easily i want to keep busy while at work i hate twiddling my thumbs at work i *need* stuff to do... so i'm doing it again, as long as someone shows me the application i'm going to go ahead and update the use cases that need to be updated, i'm the closest to it and there is nobody available to do it, so why not me? right, aside from it not actually being in my job description but isnt it better to have options open to other things than to not? i was told today that i should really just try to do my job and just my job because thats my job and they know i'll be bored but they'd rather me be bored and just do my job than to pick up the slack for others, but shouldnt i pick up the slack to get stuff done?

and out of one cheek one person says dont do that its not your job and in the next breath says hey can you do this i know its not your job but there really isnt anyone else... nifty huh?

so i'm probably going to end up doing it half, actually more than half the work is done already... so.. yeah i know