In a post this long, most people are probably going to find at least one thing they don’t like about it. I’m trying to approach this post as constructively as I can, i.e. “what I do find helpful here” rather than “how I can most effectively poke holes in this?” I think there’s enough merit in this post that the constructive approach will likely yield something positive for most people as well.
In a post this long, most people are probably going to find at least one thing they don’t like about it. I’m trying to approach this post as constructively as I can, i.e. “what I do find helpful here” rather than “how I can most effectively poke holes in this?” I think there’s enough merit in this post that the constructive approach will likely yield something positive for most people as well.
I like this comment.
I feel that EAs often have isolated demands for rigour (https://slatestarcodex.com/2014/08/14/beware-isolated-demands-for-rigor/) when it comes to criticisms.
I think the ideal way to read criticisms is to steelman as you read.
I think this post would have been significantly better as a series, partly so people could focus on/vote on the parts independently.
I don’t think it’s very surprising that 80% of the value comes from 20% of the proposed solutions.
There’s a fairly even mix of good-faith and bad-faith criticism here.
A lot of the good-faith criticism is almost a carbon copy of the winners of last year’s EA criticism contest.