Emotional Diagnosis

Responding to someone's point by naming how they supposedly feel, instead of addressing what they said.

"Hope you're doing okay, that's a lot of energy for a config file."

"Why are you so worked up about a text editor?"

"Someone's clearly taking this personally."

"Sounds like this hit a nerve."

Why It's Unproductive

Naming a feeling reframes the disagreement as a symptom, so the argument stops needing an answer. It's tempting because heated threads really do contain heated people, and the guess often feels obvious. But it leaves no reply that works: denying it reads as proof, accepting it concedes the point, and the usual result is exactly the heat it claimed to spot.

The Better Move

Answer the argument and leave the mood out of it. Someone can be annoyed and correct at the same time, and only one of those is worth replying to.

Why It's Better

It keeps the thread on the question at hand, which is the only part anyone can actually settle.

---

Examples

OP: "Three releases in a row have broken my plugins. The update process needs work."
Antipattern: "Why are you so worked up about a text editor?"
Better: "Which plugins? The API churn in 4.2 broke mine too, but if it's older ones that might be something else."

OP: "The sample was 19 people, all undergrads. That's not enough to claim a general effect."
Antipattern: "Why does a sample size make you this angry?"
Better: "19 is small, though it was within-subjects, which buys back some power. Still wouldn't generalize past undergrads."

OP: "The new checkout hides the order total until the final step. That's a dark pattern."
Antipattern: "Someone's having a bad day."
Better: "Total is on the cart page, it just doesn't follow you through checkout. That's sloppy more than dark pattern, but it should carry through."