2014 karmaJoined Jan 2023


Sorted by New
· 9d ago · 1m read



I like how you're characterizing this!

I get that the diagram is just an illustration, and isn't meant to be to scale, but the EA portion of the GHD bubble should probably be much, much smaller than is portrayed here (maybe 1%, because the GHD bubble is so much bigger than the diagram suggests). This is a really crude estimate, but EA spent $400 million on GHD in 2021, whereas IHME says that nearly $70 billion was spent on "development assistance for health" in 2021, so EA funding constitutes a tiny portion of all GHD funding.

I think this matters because GHD EAs have lots and lots of other organizations/spaces/opportunities outside of EA that they can gravitate to if EA starts to feel like it's becoming dominated by AI safety. I worry about this because I've talked to GHD EAs at EAGs, and sometimes the vibe is a bit "we're not sure this place is really for us anymore" (especially among non-biosecurity people). So I think it's worth considering: if the EA community further grows the AI safety field, is this liable to push non-AI safety people—especially GHD people, who have a lot of other places to go—out of EA? And if so, how big of a problem is that?

I assume it would be possible to analyze some data on this, for instance: are GHD EAs attending fewer EAGs? Do EAs who express interest in GHD have worse experiences at EAGs, or are they less likely to return? Has this changed over time? But I'd also be interested in hearing from others, especially GHD people, on whether the fact that there are lots of non-EA opportunities around makes them more likely to move away from EA if EA becomes increasingly focused on AI safety.

What are examples of behaviors you engage in that you suspect are inconsistent with the values/behaviors most EAs would endorse, but that you endorse doing (i.e., because you disagree to some extent with standard EA values, or because you think that EAs draw the wrong behavioral conclusions on the basis of EA values)?

Examples would (probably) not be: "I donate to political campaigns because I think this may actually be high EV" [not inconsistent with EA values] or "I eat meat but feel bad about it" [not endorsed] 

Examples might be: "I donate to a local homeless shelter because it's especially important to me to support members of my community" [deviates from standard EA values] or "I eat chickens that were raised on a local farm because I think they have good lives" [different behavioral conclusions]

I look forward to reading your point-by-point response. I suspect you will convince me that some of the events described in this post were characterized inaccurately, in ways that are unflattering to Nonlinear. However, I think it is very unlikely you will convince me that Nonlinear didn't screw up in several big, important ways, causing significant harm in the process (for reasons along these lines). 

I would thus strongly encourage you to also think about what mistakes Nonlinear made, and what things it is worth apologizing for. I think this would be very good for the community, since it would help us gain better insight into what went wrong here, and how to avoid similar situations going forward.

Fair enough! I think this discussion is being harmed by ambiguity about the behaviors we're talking about (this is my fault; my posts have been unclear). I don't think I'd classify "helping new hires find housing" as violating "standard/reasonable professional norms." 

I'm mainly thinking about the kinds of behaviors EAs engage in that are described in the above post (and my general heuristics about the kinds of practices that are normalized in the EA community). I do think that if you're asking yourself something like "Should I live with my employee who has less power than me?" or "Should I use drugs with these colleagues?" it is better to err on the side of not doing this kind of stuff, at least at first. If after a year of working with people, you all decide to start smoking weed together, that strikes me as probably pretty innocuous (versus if you had established this kind of culture at the outset). 

Thanks for your perspective on this!

Small-seeming requirements like "new hires have to find their own housing" can easily make the difference between being able to move quickly vs. slowly on some project that makes or breaks the company.

Do you have an example of this? It is surprising to me that maintaining reasonable/standard professional norms could actually sink a company. (Among other things because at a small company, you have limited manpower, and so personnel time devoted to helping someone find housing is presumably coming out of time spent somewhere else—i.e., working on the time-sensitive project.)

1): As my company has grown, we have had many forces naturally pushing in the direction of "more professional": new hires tend to be much more worried about blame about doing things too quick-and-dirty rather than incurring costs on the business in order to do things the buttoned-up way; I've stepped in more often to accept a risk rather than to prevent one although I certainly do both!

I suspect we're just defining "professional" differently here (or thinking about really different professional contexts), but my experience is pretty strongly informed by having worked in an office pre-COVID, and seeing how profoundly professional culture has eroded, and how hard it has been to build any of that back. I think grad students/academics who have taught undergrads post-COVID have also been struck by this: it seems like norms within education quickly (and understandably!) became quite lax during COVID, but it's been quite difficult to reverse those changes (i.e., get students to turn stuff in on time, respond to emails, show up to mandatory events, etc). That said, I know that older people have always tended to think that the youth are a bunch of degenerates, so plausibly that's coloring our perception here, too.

I think I largely agree with this list, and want to make a related point, which is that I think it's better to start with an organizational culture that errs on the side of being too professional, since 1) I think it's easier to relax a professional culture over time than it is to go in the other direction and 2) the risks of being too professional generally seem smaller than the risks of being insufficiently professional.

Yeah, again, I think you might well be right on the substance. I haven't tweeted about this and don't plan to (in part because I think virality can often lead to repercussions for the affected parties that are disproportionate to the behavior—or at least, this is something a tweeter has no control over). I just think EA has kind of a yucky history when it comes to being prescriptive about where/when/how EAs talk about issues facing the EA community. I think this is a bad tendency—for instance, I think it has, ironically, contributed to the perception that EA is "culty" and also led to certain problematic behaviors getting pushed under the rug—and so I think we should strongly err on the side of not being prescriptive about how EAs talk about issues facing the community. Again, I think it's totally fine to explain why you yourself are choosing to talk or not talk about something publicly.

I think the substance of your take may be right, but there is something that doesn't sit well with me about an EA suggesting to other EAs (essentially) "I don't think EAs should talk about this publicly to non-EAs." (I take it that is the main difference between discussing this on the Forum vs. Twitter—like, "let's try to have EA address this internally at least for now.") Maybe it's because I don't fully understand your justification—"there is room for people to walk back and apologize"—but the vibe here feels a bit to me like "as EAs, we need to control the narrative around this ('there is an appropriate level of publicity,')" and that always feels a bit antithetical to people reasoning about these issues and reaching their own conclusions.

I think I would've reacted differently if you had said: "I don't plan to talk about this publicly for a while because of x, y, and z" without being prescriptive about how others should communicate about this stuff.  

Yeah, my thought is pretty high-level, basically: a lot of professional norms exist for good reasons, and if we violate them—and especially if we violate a lot of them at the same time, as happened here—then this produces the kinds of circumstances in which these disputes tend to arise. 

Certainly, there's some cost-benefit here with respect to specific norms, and specific contexts, that could be, and I'm sure will continue to be, litigated. But everyone involved has been really harmed by thisin terms of their time being wasted, emotional energy sunk into this, and people's reputationsand that just seems really unfortunate, given that it is not that hard to substantially reduce the risks of these kinds of things happening by adhering to standard professional norms.


This situation reminded me of this post, EA's weirdness makes it unusually susceptible to bad behavior. Regardless of whether you believe Chloe and Alice's allegations (which I do), it's hard to imagine that most of these disputes would have arisen under more normal professional conditions (e.g., ones in which employees and employers don't live together, travel the world together, and become romantically entangled). A lot of the things that (no one is disputing) happened here are professionally weird; for example, these anecdotes from Ben's summary of Nonlinear's response (also the linked job ad):

  • "Our intention wasn't just to have employees, but also to have members of our family unit who we traveled with and worked closely together with in having a strong positive impact in the world, and were very personally close with."
  • "We wanted to give these employees a pretty standard amount of compensation, but also mostly not worry about negotiating minor financial details as we traveled the world. So we covered basic rent/groceries/travel for these people."
  • "The formal employee drove without a license for 1-2 months in Puerto Rico. We taught her to drive, which she was excited about. You might think this is a substantial legal risk, but basically it isn't"
  • "The semi-employee was also asked to bring some productivity-related and recreational drugs over the border for us. In general we didn't push hard on this."

I am reminded again that, while many professional norms are stupid, a lot of them exist for good reasons. Further, I think it's often pretty easy to disentangle the stupid professional norms from the reasonable professional norms by just thinking: "Are there good reasons this norm exists?" (E.g., "Is there a reason employees and employers shouldn't live together?" Yes: the power dynamics inherent to the employer/employee dynamic are at odds with healthy roommate dynamics, in which people generally shouldn't have lots of power over one another. "Is there a reason I should have to wear high heels to work in an office?" .... no.) Trying to make employees part of your family unit, not negotiating financial details with your employees, covering your employees' rent and groceries, and being in any way involved in your employees breaking the law are all behaviors that are at odds with standard professional practices, and there are very obviously good reasons for this.

Load more