If you want this to be really useful (seems unlikely, frankly), brevity is key. The code needs to "reproduce the problem".

"This is a little long" *bing* large portion of audience reads no further.

Replace "that demonstrates your problem" with "that reproduces the problem" ?? Seems very reasonable to me.

re "*bing*" -- that's probably true, and I will seek an alternate introduction... perhaps by s/This is ... scan it. It's/This is.../. (You may not really satisfied with that, either; neither am I.)

Re the length -- well, maybe I should overcome the "laziness" I mentioned above, and do an initial Markup in the Monastery-like precis.

Sometimes "brevity" !eq ("precision" | "comprehensiveness" | "actually helpful")

Sometimes "brevity" !eq ("precision" | "comprehensiveness" | "actually helpful")

Of course. But for a node meant to be read by a new poster who has a problem that they want an answer to, "not extremely brief" directly leads to "going to be ignored by most of the target audience" which makes it not "really useful", IMO (though it will surely still be useful for people who like to write boiler-plate replies).

Replace "that demonstrates your problem" with "that reproduces the problem" ??

Sorry, the text was too long for me to spare the time to read it. That is why I only commented on a (brief) reply (I just searched for "reproduce" -- which is a clearer word to use than "demonstrate"). Augmenting an erroneous "must compile" instruction with yet another paragraph is certainly going in the wrong direction.

- tye