I think the layout of this post is quite reader unfriendly.
I strongly suggest you start with a full summary rather than just an intro, and don’t bury your conclusions midway between the post and some very long appendices which are unlikely to be very useful to 90% of readers.
As it is, anyone wishing to respond in depth would basically have to do the work of summarizing the post themselves, which increases the friction on feedback.
I agree! As noted under Richard’s comment, I’m afraid my only excuse is that the points covered are scattered enough that writing a short, accessible summary at the top was a bit of a pain, and I ran out of time to write this before I could make it work. (And I won’t be free again for a while…)
If you or anyone else reading this manages to write one in the meantime, send it over and I’ll stick it at the top.
I think the layout of this post is quite reader unfriendly.
I strongly suggest you start with a full summary rather than just an intro, and don’t bury your conclusions midway between the post and some very long appendices which are unlikely to be very useful to 90% of readers.
As it is, anyone wishing to respond in depth would basically have to do the work of summarizing the post themselves, which increases the friction on feedback.
I agree! As noted under Richard’s comment, I’m afraid my only excuse is that the points covered are scattered enough that writing a short, accessible summary at the top was a bit of a pain, and I ran out of time to write this before I could make it work. (And I won’t be free again for a while…)
If you or anyone else reading this manages to write one in the meantime, send it over and I’ll stick it at the top.