No, not really. I meant by the prose description of how to optimise the code. It felt like how chess masters may discuss their strategies after a game of chess. Very high level and far from what a layperson may really understand about chess (or optimising), but very true and distinct nonetheless.
It gives a glimpse into the mind of the chess master (or optimiser) even when you yourself don't possess these skills.
Oh okay. I see the similarity now - it does look like prose discussion of chess games. The analogy can be pretty deep, like strategic considerations ("opposite-colored bishops" vs "spread-out dependent instructions" in the prose you replied to). Thanks for the clarification, this was insightful.
It gives a glimpse into the mind of the chess master (or optimiser) even when you yourself don't possess these skills.