I am trying to go deeper with org mode to the literate coding stuff itself rather than merely for markup.
I am writing a document where I'm solving some coding challenge, and part way through reasoning about it, decide to take an aside to ensure that I know how to pass tables into src blocks and to use sessions. The next section of my document is a sort of "aside" where I am testing just that (though using some of the named tables in the containing header). I then want to return to solving the problem.
So I have
* My problem writing src block writing a-named-table more writing here's my aside, writing src block writing src writing src writing, back to the main thing, I'm not referencing anything in the aside here
What is a good way of denoting that aside so that I can expand/collapse it and control whether I want it exported or not later?
I could use a headline but then returning to the main code would require its own headline which would be weird in the outline as it would split up what is one logical flow of thought into two simply because an aside was nestled between.
I use asides in writing prose a lot so I think it would probably be beneficial for my literate coding efforts to know the "right" way of doing it.