I think my comment in response to Raemon is applicable here as well. I found your argument as to why progress studies writ large is important persuasive. However, I do not feel as though this post is the correct way to go about that. Updating towards believing that progress studies are important has actually increased my conviction that this post should not be collated: important areas of study deserve good models, and given the diversity of posts in progress studies, the exact direction is still very nebulous and susceptible to influences like collation.
The most significant objection I have to the structure of this post is that I feel like it’s a primer/Wikipedia page, not a post explaining a specific connection. Both of the examples you provide explain the relevance of the natural system at hand to a core LessWrong discussion topic. The failure mode I’m worried about with this type of post is that there are a lot of things that have contributed to human progress, meaning that this type of historical brief could easily proliferate to an excessive extent. Like I mentioned to Raemon, I’d feel a lot better about this post if it discussed how this gear meshed with broader historical/progress trends, because then it would be a more useful tool for developing intuition. Using the spitballed three-prong test, the first post is definitely not replaceable with Wikipedia, and arguably relevant to LessWrong (though I think that condition is underspecified), and the section post is similarly acceptable, in my eyes. I’d support collation of more progress studies posts, just not this one.
Ok, I think our crux here is about how much posts should explicitly point out how their material connects to everything else.
Personally, I think there’s a lot of value in posts which explicitly do not explain how they connect, because explaining connections usually means pulling in a particular framing and suggesting particular questions/frameworks. In a pre-paradigmatic field, we don’t know what the right questions or frames are, so there’s a lot of value in just presenting the information without much framing. It’s the “go out and look at the world” part of rationality.
Now, a downside of this sort of post is that many people will come along who don’t have any idea how the material relates to anything. There’s no hand-holding in the interpretation/connections, so readers have to handle that part on their own, and not everyone is going to have enough prior scaffolding to see why the material matters at all. (I’ve definitely seen this on many of my own posts, when I present a result without explaining how it fits in with everything else.)
I think the best way to handle this sort of trade-off is to have some posts which present information (especially concrete examples) without much framing, and then separately have posts which try to frame that information and explain how things fit together (which usually also means positing hypotheses/theories). It’s very similar to the separation of empirical vs theoretical work we see in a lot of the sciences. We already have a lot of the latter sort of post, but could use a lot more of the former. So e.g. “this type of historical brief could easily proliferate to an excessive extent” is something I’d consider a very positive outcome.
I think you’re mostly right. To be clear, I think that there’s a lot of value in unfiltered information, but I mostly worry about other topics being drowned out by unfiltered information on a forum like this. My personal preference is to link out or do independent research to acquire unfiltered information in a community with specific views/frames of reference, because I think it’s always going to be skewed by that communities thought, and I don’t find research onerous.
I’d support either the creation of a separate [Briefs] tag that can be filtered like other tags, and in that case, I’d support this kind of post, but at the moment, I don’t know what the value add is for this to be on LessWrong, and I see several potential costs.
I think my comment in response to Raemon is applicable here as well. I found your argument as to why progress studies writ large is important persuasive. However, I do not feel as though this post is the correct way to go about that. Updating towards believing that progress studies are important has actually increased my conviction that this post should not be collated: important areas of study deserve good models, and given the diversity of posts in progress studies, the exact direction is still very nebulous and susceptible to influences like collation.
The most significant objection I have to the structure of this post is that I feel like it’s a primer/Wikipedia page, not a post explaining a specific connection. Both of the examples you provide explain the relevance of the natural system at hand to a core LessWrong discussion topic. The failure mode I’m worried about with this type of post is that there are a lot of things that have contributed to human progress, meaning that this type of historical brief could easily proliferate to an excessive extent. Like I mentioned to Raemon, I’d feel a lot better about this post if it discussed how this gear meshed with broader historical/progress trends, because then it would be a more useful tool for developing intuition. Using the spitballed three-prong test, the first post is definitely not replaceable with Wikipedia, and arguably relevant to LessWrong (though I think that condition is underspecified), and the section post is similarly acceptable, in my eyes. I’d support collation of more progress studies posts, just not this one.
Ok, I think our crux here is about how much posts should explicitly point out how their material connects to everything else.
Personally, I think there’s a lot of value in posts which explicitly do not explain how they connect, because explaining connections usually means pulling in a particular framing and suggesting particular questions/frameworks. In a pre-paradigmatic field, we don’t know what the right questions or frames are, so there’s a lot of value in just presenting the information without much framing. It’s the “go out and look at the world” part of rationality.
Now, a downside of this sort of post is that many people will come along who don’t have any idea how the material relates to anything. There’s no hand-holding in the interpretation/connections, so readers have to handle that part on their own, and not everyone is going to have enough prior scaffolding to see why the material matters at all. (I’ve definitely seen this on many of my own posts, when I present a result without explaining how it fits in with everything else.)
I think the best way to handle this sort of trade-off is to have some posts which present information (especially concrete examples) without much framing, and then separately have posts which try to frame that information and explain how things fit together (which usually also means positing hypotheses/theories). It’s very similar to the separation of empirical vs theoretical work we see in a lot of the sciences. We already have a lot of the latter sort of post, but could use a lot more of the former. So e.g. “this type of historical brief could easily proliferate to an excessive extent” is something I’d consider a very positive outcome.
I think you’re mostly right. To be clear, I think that there’s a lot of value in unfiltered information, but I mostly worry about other topics being drowned out by unfiltered information on a forum like this. My personal preference is to link out or do independent research to acquire unfiltered information in a community with specific views/frames of reference, because I think it’s always going to be skewed by that communities thought, and I don’t find research onerous.
I’d support either the creation of a separate [Briefs] tag that can be filtered like other tags, and in that case, I’d support this kind of post, but at the moment, I don’t know what the value add is for this to be on LessWrong, and I see several potential costs.
Good suggestion, and I expect some mechanism along these lines will show up if and when it becomes significant.