I too agree with the editorial..

It is far too often WAY MORE damaging to jump into a fix without proper consideration than it is to stop and think about it.

Case in point, a recent discussion here about a database that was suspect and some questionable advice on how to fix it. That advice failed to cover WHY the database was suspect and that a little bit of research BEFORE action was REQUIRED.

And when management is squealing about how bad they need this fixed remaining calm and getting it fixed RIGHT THE FIRST TIME helps give them the confidence to let you do your job, not always but it helps.

And I've had a stack of people in my cubie before just watching me type, to the point I turned around and said, "listen, I'm going as fast as I can, you standing there isn't going to make this go any faster. I will let you know when I know something." Which was the subtlest way I could say SCRAM, I'M WORKING HERE..

CEWII