Hacker News Reader

Comment by fastball | Hacker News Reader

My impression was that it was the employees who wouldn't let it go, not DHH. And one employee in particular wouldn't let it go, so DHH helpfully pointed out that at some point they too had participated in joking about a customer name, so who exactly were they trying to persecute here?

View on HN

I saw that too, and that I think was such a crucial mistake. Discretion, as they say, is the better part of valor. Is it fun to point out someone's hypocrisy? Probably. Is it going to be productive, especially to do so in a public manner? Absolutely, absolutely not. You're embarrassing them, to what, teach them a lesson? Well, lesson learned, but not the one you intended -- they'll learn that the boss is not above a little public humiliation to score a point. Trust gone. I'd sure start looking for other places if my manager, or the CTO, started doing that, severance or no.

I mean I don't trust hypocrites in the first place, so I'm not sure it's the boss that broke the trust.

One thing that I think gets lost in discussions of hypocrisy is that there are actually two types, and they should be handled very differently.

The first type is when an alcoholic tells you to slow down on your drinking, e.g. "do as I say and not as I do" hypocrisy. This kind is usually ok, because it tends to be more of a "learn from my mistakes" situation than a failure to understand the contradiction in your own words.

The second type is "rules for thee and not for me" hypocrisy – people that try to catch others out in their "bad behavior" but then think it is totally fine when they do it themselves, as they provide some sort of post-hoc rationalization for why it is ok for them to do it ("because context" or whatever) but totally unacceptable for others to do so.

Most people conflate the two types, but I try to only refer to the latter type as hypocrisy, and I think it is generally bad to be a hypocrite in that way. And from the sounds of it, the Basecamp employees in question were definitely more of the latter than the former.

I get your argument, but "oh, sure, you're calling me out, but you did this similar thing earlier, hah!" is not going to de-escalate conflict. Isn't part of being a manager in a prickly situation learning to choose your battles? If he'd just dropped it at that point, would there have really been any harm done to the company? Would that harm have been greater than the end result we've arrived at instead?

The damage done to Basecamp's public reputation, internal morale, and now all the projects set back by losing a third of their employees is unfathomable -- all for the satisfaction of "by gum, at least I don't have to say I put up with one of my now-former employees talking back to me in a way that was arguably hypocritical." On balance, was that really the right tradeoff to make here?

I get you, but I think you're assuming the point was to point out hypocrisy for the sake of hypocrisy, when the actual point of pointing out hypocrisy in this case was to ask the question: "What exactly is your goal here? Do you want me to fire everyone who made fun of customer names? Because if so that means I'm firing you too. Any response to this situation will involve disciplining you too, so what are you trying to accomplish?"

This was my reading as well - from the post that DHH shared.

What do you do when a (previously-complicit) employee keeps an issue going on and on and on?

A little 'hey, get off your high horse, you were involved too' doesn't go amiss.

(As a first, second or even third reaction it's not great - but it sounds like there had been a lot of talking preceding this).

Reply on news.ycombinator.com