I don’t think it’s possible to write a single page that gives the right message to every user
My own attempt to solve this is to have the article MAINLY split up into sections that address different readers, which you can skip to.
2.
the second paragraph visible on that page is entirely caveat.
2.2. [edit: seems like you agree with this. TL;DR: too many caveat already] My own experience from reading EA material in general, and 80k material specifically, is that there is going to be lots of caveat which I didn’t (and maybe still don’t) know how to parse. it feels almost like how people are polite in the U.S (but not in Israel), or like fluff in emails, I’m never sure how to understand it, so I mostly skip it
2.3. [more important] I think there’s a difference between saying “we’re not sure” and saying “here’s a way that reading this advice might do you more harm than good” (which I personally often write in my docs (example), including something I wrote today)
I don’t think it’s worth me going back and forth on specific details, especially as I’m not on the web team (or even still at 80k), but these proposals are different to the first thing you suggested. Without taking a position on whether this structure would overall be an improvement, it’s obviously not the case that just having different sections for different possible users ensures that everyone gets the advice they need.
For what it’s worth, one of the main motivations for this being an after-hours episode, which was promoted on the EA forum and my twitter, is that I think the mistakes are much more common among people who read a lot of EA content and interact with a lot of EAs (which is a small fraction of the 80k website readership). The hope is that people who’re more likely than a typical reader to need the advice are the people most likely to come across it, so we don’t have to rely purely on self-selection.
Hey Alex :)
1.
My own attempt to solve this is to have the article MAINLY split up into sections that address different readers, which you can skip to.
2.
2.2. [edit: seems like you agree with this. TL;DR: too many caveat already] My own experience from reading EA material in general, and 80k material specifically, is that there is going to be lots of caveat which I didn’t (and maybe still don’t) know how to parse. it feels almost like how people are polite in the U.S (but not in Israel), or like fluff in emails, I’m never sure how to understand it, so I mostly skip it
2.3. [more important] I think there’s a difference between saying “we’re not sure” and saying “here’s a way that reading this advice might do you more harm than good” (which I personally often write in my docs (example), including something I wrote today)
I don’t think it’s worth me going back and forth on specific details, especially as I’m not on the web team (or even still at 80k), but these proposals are different to the first thing you suggested. Without taking a position on whether this structure would overall be an improvement, it’s obviously not the case that just having different sections for different possible users ensures that everyone gets the advice they need.
For what it’s worth, one of the main motivations for this being an after-hours episode, which was promoted on the EA forum and my twitter, is that I think the mistakes are much more common among people who read a lot of EA content and interact with a lot of EAs (which is a small fraction of the 80k website readership). The hope is that people who’re more likely than a typical reader to need the advice are the people most likely to come across it, so we don’t have to rely purely on self-selection.