It may not be possible to cleanly divide the Technical Explanation2 into multiple posts that each stand on their own, but even separating it awkwardly into several chapters would make it less intimidating and invite more comments.
(I think this may be the longest post in the Sequences.)
I can’t help but think of Scott Alexander’s long posts, where usually there’s a division of topics between roman-numeraled sections, but sometimes it seems like it’s just “oh, it’s been too long since the last one, got to break it up somehow”. I do think this really helps with readability; it reminds the reader to take a breath, in some sense.
Or like, taking something that works together as a self-contained thought but is too long to serve the function of a paragraph, and just splitting it by adding a superficially segue-like sentence at the start of the second part.
It may not be possible to cleanly divide the Technical Explanation2 into multiple posts that each stand on their own, but even separating it awkwardly into several chapters would make it less intimidating and invite more comments.
(I think this may be the longest post in the Sequences.)
Do you have any ideas on how you’d go about this? I’m tackling this post this week for the print version of R:AZ and am definitely intimidated :)
I can’t help but think of Scott Alexander’s long posts, where usually there’s a division of topics between roman-numeraled sections, but sometimes it seems like it’s just “oh, it’s been too long since the last one, got to break it up somehow”. I do think this really helps with readability; it reminds the reader to take a breath, in some sense.
Or like, taking something that works together as a self-contained thought but is too long to serve the function of a paragraph, and just splitting it by adding a superficially segue-like sentence at the start of the second part.