This is a pretty high barrier to entry. I agree that we should encourage reading the sequences, but should we phrase it in another way so that we still welcome participation?
I think that barrier is about right. We do welcome participation, but only from people who have taken the trouble to find out, from the material we direct them to, what we’re about.
I’ve seen similar language on several technical discussion forums: people are asked to read the FAQs and not to retread old ground.
I have also seen similar language on other sites, but the the sequences are a lot longer than what I have seen other sites asking new visitors to read.
I had read OB when EY still used to blog there, so I read a lot of the sequences at that time. Stretched out over time like that, they don’t seem as long. But for a brand new visitor, the sheer volume is somewhat daunting. That’s why I think more nuanced suggestions, perhaps like Jack suggests here, might make sense.
I think that barrier is about right. We do welcome participation, but only from people who have taken the trouble to find out, from the material we direct them to, what we’re about.
I’ve seen similar language on several technical discussion forums: people are asked to read the FAQs and not to retread old ground.
I have also seen similar language on other sites, but the the sequences are a lot longer than what I have seen other sites asking new visitors to read.
I had read OB when EY still used to blog there, so I read a lot of the sequences at that time. Stretched out over time like that, they don’t seem as long. But for a brand new visitor, the sheer volume is somewhat daunting. That’s why I think more nuanced suggestions, perhaps like Jack suggests here, might make sense.