Many times I stumble upon well-formatted and perhaps even clearly written questions. Sometimes it is even the asker, that did everything properly from the start, and not a moderator, that corrected the formatting. However, what they truly lack, is a minimal working example.
One example of such a question is here.
The OP is reasonably well formatted, the equations are certainly readable. The code-block is quite bad due to copy-paste issues (linebreaks with
\ and excessive use of subscripts), but that's understandable, many people new to MMA stumble into these pits.
When I encounter something like that in a review queue, I'm uncomfortable with voting to close, because I struggle to justify it. That is, it'll take too much work to figure out whether there's just a simple mistake somewhere or maybe the question is perfectly valid and just really is that difficult, that it needs to be that long. Therefore I usually click on "Skip".
Today, however, I had a change of heart with the linked question. In my opinion, it is
In part, not about MMA, even though the solution is to be obtained with the help of the software.
The code is extremely hard to read and the equations in TeX form are not really straightforward for reduction to a MWE.
It just takes too much effort, really, to fathom out the problem in what essentially is a code-dump.
So I voted to close, because I felt this is work for a "professional consultant". However, I'm not sure, if that's really the right way to go. Maybe I should have simply downvoted on that question. Maybe I should have taken no action at all.
Upvote the question if you feel, this is a true problem, downvote if I'm making something out of nothing, and when answers come, upvote those, you think offer a good approach to this.