patrickmcginnis59 10839 (4/18/2013)

---

djackson 22568 (4/18/2013)

---

patrickmcginnis59 10839 (4/18/2013)

---

Eric M Russell (4/18/2013)

An IT guy who can't perform under pressure is next to useless, even if he's smart.

I have to admit, I don't like to work under pressure. What sort of situations would you consider to be a "pressure" generating duty?

I can't imagine working like that. Pressure is a daily occurrence where I work, and always has been. Sometimes it is excessive, usually due to senior management going too long without adapting to new realities. Some days I have multiple "critical" systems go down at the same time.

Well is it a pressure situation? I've been in that situation, what the heck else can you do but work on the problem? If you've got a pretty good team going, everyone searches for solutions. I just had one situation where I helped fix a problem with a switch, we were ABSOLUTELY shut down, and I helped with syntax for some router filtering, and for that matter, I'm not even normally involved with networking since I normally function as the department DBA. If I had read the docs "faster" because I was "under pressure" then I'm certain that I would subsequently be less effective.

Now I've made a few mistakes that put me "under pressure," but I DON'T ENJOY MAKING MISTAKES AND DO MY BEST TO AVOID THEM. But really, what can you do with flat out errors in the first place? Errors have consequences after all.

It could be the case that these "pressure" situations are in reality disfunctional work environments, and I do have to admit as in my original post I don't like to work in those situations.