Sunday, October 2nd, 2011 10:27 pm
the history of work relations
I have come to the very uncomfortable realization that I am apparently adapting to breakneck release schedules; most recently, I was completely unalarmed when I had to do a requirements meeting a week before code freeze (aka, the last day that we can test and expect anything will get fixed before release). Requirements, by the way, are just a glorified numbered list of What This Particular Change to the Program Will Do.
( testing is for people who love frustration )
I can't actually tell if I'm good at my job, but I'm pretty sure I'm competent at it, at least from how much I'm given to do (or you know, not a lot of people to do the work could also be a factor), but I do like the fact that more personal interaction with a few of the developers--and their willingness to respond quickly and willingness to listen and watch a demonstration of a problem before making a proclamation on it (surprisingly rare) has been far more effective than I ever imagined in regard to getting a working program.
( slight personal digression on one developer )
( testing is for people who love frustration )
I can't actually tell if I'm good at my job, but I'm pretty sure I'm competent at it, at least from how much I'm given to do (or you know, not a lot of people to do the work could also be a factor), but I do like the fact that more personal interaction with a few of the developers--and their willingness to respond quickly and willingness to listen and watch a demonstration of a problem before making a proclamation on it (surprisingly rare) has been far more effective than I ever imagined in regard to getting a working program.
( slight personal digression on one developer )