I'm glad to say I've been successfully staying stressed without having to know about these tips. I guess I'm just naturally talented at it, it's one of my key strengths.
I know you are being a bit sarcastic, but being stressed in this manner can actually be a strength if you know how to turn it off. I am quite productive when I stress myself, and as long as I can easily relax when the time comes (when the work is done), I think I will remain healthy. (I still have my hair, after all.)
As someone whose stress has almost wrecked his life, I can relate to many of these points.
The levels of stress that I have can be debilitating and actually keep me from doing my work. It's useful to see lists like this to remind myself of what I should be avoiding.
They aren't really conflicting. The middle-ground coms from recognizing things that really are your responsibility, while ignoring the parts that have nothing to do with you. Basically they are extremes to be avoided. Taking some criticism is probably a good idea -- it can be helpful. Similarly passing blame even when the problem is your fault is probably a bad idea.
Say, for instance, you are on a project with a couple other developers. Your main responsibilities have been features a, b, and c. Further you noticed d and e were pretty messed up, and helped a junior developer start straightening them out. Some milestone is reached, and you have a code review with the senior dev (who is one of those arrogant guys who may be pretty good, but is also a condescending asshat). He says "your factoring on a,b, and c could be done this way instead, how could you not see something so simple. As for d and e you really screwed the pooch there".
The extremes would be "Gosh i am stupid, I really messed up factoring and features, I need to work 80 hour weeks to make up for it" and "It was all junior dev's fault -- if only he didn't need help i could have factored right, and you wouldn't even think to talk to me about d and e." In reality (reconciling the two statements) a good approach would ignore the stupidity insinuation, acknowledge that the factoring could be better, and say "Listen d and e aren't even mine, I'm helping junior dev learn the ropes, so there are mistakes, but they're getting better, you should have seen it last week".
On a more serious note, it really does help to pull back from the extremes. I'm guilty of oscillating between thinking of myself as the absolute best or the absolute worst. Both are a struggle to live with. Or demanding absolute clarity about principles before proceeding. It's important to tolerating ambiguity. And trust in yourself to navigate even without perfect knowledge.
Seems to me that the author has tried to break it down into six groups of actions a person will do to keep themselves stressed — a kind of "personality type," if you will. He simply left out any sort of naming/header for each group.
My experience is that different personalities stay stressed in different ways. E.g., I very much tend to do the former, and have repeatedly picked partners who tended to do the latter. It sure makes for dysfunctional relationships.
I have a hard time switching my brains off. Even when i try to sleep. The problem is that having this ability is what gives me my technical abilities so its both a blessing and a curse.
Quite the opposite, I try hard to keep my brain working while dozing off and while waking up .. and as much as possible when I am drifting in and out from consciousness, because sometimes that's how I find a solution to a problem that I have been banging my head against the wall for. I think there was some research done before about the upside of some truth behind "I'll sleep on it".
I fail to understand how this can be useful. Seems an (inverse) application of an old method: to say something wise, first think of something foolish and then say the opposite.