It was about "what do we tolerate", "who do we welcome", "who are we as a company"? They didn't like their employees defining this for them, because it forced them to think things they didn't want to think about.
On the contrary, as far as I can tell (i.e., based on information released by founders and employees), they didn't object at all to being called out on it. Everybody at Basecamp, the founders included, thought the list was wrong and inappropriate.
What they did object to was the discussion being escalated to genocide and that there appear to have been employees who refused to climb down from that.
It does become impossible to have a constructive discussion, particularly about sensitive or controversial matters, when some people involved want to escalate to the most extreme position imaginable. It tends to mute other viewpoints.
This used to be well understood on the internet, and is the reason Godwin's Law is explicitly stated (https://en.wikipedia.org/wiki/Godwin%27s_law#:~:text=Godwin'....).
it feels like a problem with the discussions participants listening and speaking skills.
if someone immediately jumps to a negative extreme then its likely they feel quite emotionally distressed about the topic. if you notice someone is emotionally charged about a topic (either yourself or a participant) then we should seek to discover the shadow conversation that is being had. what is the true source of the emotional distress.
instead we see it as weakness and press harder.
removing politics won’t solve that.
It can be pretty frustrating when people debate in this fashion about work-related matters. E.g., nowadays I find it particularly tiresome when people frame technical discussions (such as one database platform or front-end technology versus another) in moral terms. It's incredibly unhelpful.
It has the potential to be even more disruptive for non-work matters (though the original "Best names ever" discussion was very much work-related).
Still, whilst I'm not especially critical of the position DHH and JF have taken - though initially I found myself back and forth on it - I do of course wonder if a more nuanced resolution that alienated fewer people (I don't mean on twitter and other social media, which is mostly just noise: I mean at Basecamp) could have been found than something that feels like blanket ban, even though it's not really.
Perhaps they tried - I don't know.
i suspect, a lot like becoming conscious of the impact the food we choose to eat has on things external to our local context (climate, animal welfare etc), technology decisions choices could be seen through such a lens.
as Frederic Bastiat wrote, there is “that which is seen and that which is not seen”.
Where do you work? Can I join?
More seriously, if you (have nothing better to do than) look through my comment history you'll find a discussion from a few weeks or months back where I chided somebody for saying (I paraphrase), "if you're patching directly in production you're doing it wrong." Granted doing so is far from ideal, and not something I've ever done with any kind of regularity, but occasionally it's the quickest way to resolve an issue whilst you follow proper process with a more involved investigation and fix.
I've found this varies a lot by company I've worked for: it doesn't happen where I work now much at all, but other companies I've worked at many technology choices are either "right" or "wrong". I just don't have the energy or patience for it these days.
in that case, yes. people get dogmatic about the strangest things. depending on my level of give-a-fuck i sometimes dive in deeper, “why do you think this is bad?” etc.
sometimes theres a decent learning opp either for me, discovering a new way that something can cause problems or for them, learning to apply some nuance to their beliefs.
And that's quite a long way from what I'm talking about, which are technical discussions that are more day to day concerns for many software developers in the industries and types of application I've worked with (e.g., desktop software tools and web applications/services in sectors such as telecoms, life science, payment processing, retail systems, data analytics).
Other companies are able to handle peer conversations without making such a broad and vague category as politics taboo. Like you can enforce a code of conduct and treat speech of genocide as being in violation and issue a citation for a minor offense and terminate repeated or hard offenders. You can also enforce stricter speech standards on open channels and announcements while allowing workers to have free conversation in their own opt-in echo chambers.
Nuking all political dialogs just feels like a bad HR policy.
I think this is what the policy amounts to though, right? They're banning political discussion on their shared work Basecamp, but not anywhere else, and are even encouraging it in other private and opt-in channels, as well as employees' personal blogs, social media, etc.
That's not actually what they've said though, is it? They're moving responsibility for DEI back into HR (they call it People Ops)[0]. I have pretty mixed feelings on HR as a company function[1] and choice of profession, but that's far from a ban on DEI initiatives.
(I don't dispute your comment that committees have been dissolved.)
[0] The original "Changes at Basecamp" blog post literally says, "The responsibility for DEI work returns to Andrea, our head of People Ops,": https://world.hey.com/jason/changes-at-basecamp-7f32afc5
The thing is, that is not very far at all. You were not involved in the situation at all.
Some employees have been critical on social media of the policy changes. None of them has suggested that DHH or JF thought it was OK that the names list existed. Again, all available evidence suggests that nobody who is still at Basecamp or who was there formerly, including the founders, thinks the names list is OK.
What exactly are you questioning here?
Because you evidently don't know any more than I do yet, based on that same body of information, you seem willing to insinuate a much shakier conclusion though you lack the courage to state it explicitly (because I think you know that it's not backed up by any evidence). You're not adding anything to the discussion other than noise.
The pyramid is intended to show that its foundational to hate.
Thats then being immediately taken out of context to equate stereotypes with genocide as a straw man argument. In this thread.
Nobody here or at Basecamp made such an argument. Its entirely made up to shut down discussion.
Thought is also the foundation below that. In fact, thought is much more requisite to hate rather than making fun of something.
Shall we update the pyramid and show that thought is the foundation to all hate so we can show it whenever someone thinks?
> What they did object to was the discussion being escalated to genocide and that there appear to have been employees who refused to climb down from that.
The topic brought up was the Pyramid of Hate, and I'm going to presume linking the list of names to one of the base levels of bias. DHH is the one who escalates that point to say, well this must be a fireable offense since it is on this pyramid with genocide on the top, which is really completely ignoring the point of the pyramid and not at all what employees probably said. An employee actually tries to explain this, that "dehumanizing behavior begins with very small actions". DHH ignores the point and completely unprofessionally and unethically (imagine the CEO of your company doing this) publicly shares some old chat log of the employee participating in making fun of the names, as if this employee wouldn't be aware of that and probably regretful of it.
So yes, an employee tried to explain what might be wrong with DHH's thinking and yes he did not like it at all and responded inappropriately and he was the one who wanted to "escalate to the most extreme position imaginable."
Here is the full-text from the article that described what happened:
"But Hansson went further, taking exception to the use of the pyramid of hate in a workplace discussion. He told me today that attempting to link the list of customer names to potential genocide represented a case of “catastrophizing” — one that made it impossible for any good-faith discussions to follow. Presumably, any employees who are found contributing to genocidal attitudes should be fired on the spot — and yet nobody involved seemed to think that contributing to or viewing the list was a fireable offense. If that’s the case, Hansson said, then the pyramid of hate had no place in the discussion. To him, it escalated employees’ emotions past the point of being productive.
Hansson wanted to acknowledge the situation as a failure and move on. But when employees who had been involved in the list wanted to continue talking about it, he grew exasperated. “You are the person you are complaining about,” he thought.
Employees took a different view. In a response to Hansson’s post, one employee noted that the way we treat names — especially foreign names — is deeply connected to social and racial hierarchies. Just a few weeks earlier, eight people had been killed in a shooting spree in Atlanta. Six of the victims were women of Asian descent, and their names had sometimes been mangled in press reports. (The Asian American Journalists Association responded by issuing a pronunciation guide.) The point was that dehumanizing behavior begins with very small actions, and it did not seem like too much to ask Basecamp’s founders to acknowledge that.
Hansson’s response to this employee took aback many of the workers I spoke with. He dug through old chat logs to find a time when the employee in question participated in a discussion about a customer with a funny-sounding name. Hansson posted the message — visible to the entire company — and dismissed the substance of the employee’s complaint."
Not at all true - they dealt with it extensively internally, agreed it shouldn't have happened, etc. But folks kept analogizing the list of funny name to genocide.
I think its been properly debunked multiple times in the comments here to say its untrue. Just wondering where it comes from that people keep commenting it so strongly.
Not if you're one of the injured parties.
If you don't believe me, well, DHH himself agrees with this: it's a problem when you acknowledge the pyramid of hate, as he does.
What's at issue is that he acknowledges all of this, then refuses to recognize any wrongdoing, dresses down employees in public, and claims that "political talk" -- about the company, about whether these practices are correct, about whether this is an inclusive and equal place -- is banned.
They're not necessarily ethnic, some people just have funny names:
https://theawesomedaily.com/50-funny-names-that-are-so-unfor...
https://www.newidea.com.au/funny-names
In your opinion just how genocidal are these articles on the pyramid of hate?
I'll be frank- and I know that I'm risking the mistake of reading just what I want to read-, I think that those "counter to creating an inclusive workplace" and the general tone ("serious collective failure" etc.) are just nods to the social justice culture, and are meant to appease and concede some ground to the opponent. I don't think (also because it is clearly stated elsewhere in the same post) that there was anything intrinsically racist in that list, or anything that made it substantially different from those examples above. Apart from the obvious difference that these are customers, and it's not nice to secretly make fun of them.
The first list you posted has a bunch of "funny" East Asian names. That stuff was racist in "Sixteen Candles," there's no excuse for it in a modern workplace.
1) that the list was a mistake and that they've learned and moved on.
2) that "I was dismayed to see the argument advanced in text and graphics on [Employee 1’s] post that this list should be considered part of a regime that eventually could lead to genocide. That's just not an appropriate or proportionate comparison to draw"
3) that "the vast majority" of the names in the list were in fact of Anglo-Saxon or white background.
So he acknowledges, apologises and de-escalates. And points out that there is nothing racial about the list. What should he have done more, or differently?
To your question, I think it is the consequences of closing such a discussion that he leaves unaddressed. Does the company still value your opinion? Do you matter?
I honestly think, as DHH hints, that being able to 'rehumanize' might avoid even having to ask these questions.
It seems he clearly proved that those opinions matter, if he recognized the mistake, recognized the validity of some of the points made, and apologised.
What I've observed in this and other well known instances of "social justice" protests (I hope it's the best neutral term to describe them) is that there seems to be no endgame accepted by the protesters. No apologies are ever accepted without an explicit or implicit transfer of power to them. An example of an explicit transfer of power is setting up some commission or bureaucratic structure where the protesters or people they trust will be enrolled; and resignations represent an implicit transfer of power (the recognized power to make someone lose their job, which is not a small one).
Compare this with normal workplace dynamics. You can complain inside your workplace for many work-related reasons (workload, bad management, pay, etc.). Your complaints can be openly discussed, legitimately rejected, or acted upon. But in any case a change in the hierarchy or in the company structure is not something you expect. It can happen (very rarely) or not, and you might be satisfied with the responses or the changes or not, and if you don't like the answers after a while you might decide to move somewhere else. You don't consider unacceptable that the company doesn't see or address your point of view. At some point the discussion ends and that's it. This is not what happens on social justice complaints, and I think it's toxic (in the workplace, but in general everywhere).
What DHH neglects to address is that he's claiming the power to silence. "we had to close down this channel" or "discussions are being moved".
I like your idea of comparing this to a normal workplace dynamic. What if you get the rare change you wanted to see, but in exchange there is a new policy: no more discussions like this? Yes, your ideas about devops or whatever were fine, we're making a change, and now please never discuss our product development process again.
At the very least, does the change you 'won' feel genuine?
It's unprofessional, shouldn't have been done, we're stopping it, if people recreate it that will have appropriate consequences. Done. What's the point of even mentioning this trivial thing again?
I'm not even saying it's a cynical play, it's extremely easy to forget to reflect on it and just think you're doing the right thing all along. The outcome is still the same though.
Two other details I find interesting:
- In the post you linked to, DHH specifically talks about the Asian names on the list.
- The only attributed statements I've seen from any non-founder employees are from Jane Yang.
Might well be, and yet this doesn't mean the "white men" are always wrong. If the vast majority of the names in the list belong to Western whites, and only a few to Asians, does it make sense to claim the list is racist? I don't think so. And why should someone admit (and thus confirm) a non-existent but very serious moral failing, just to appease an angry employee? With all that it entails: once something has been confirmed to be a moral failing, the same judgement automatically applies to all similar instances. We're seeing where this is going.