I think @JeremyLT is trying to push people to properly describe the issue they are having rather than us having to work it out ourselves. I can see both points of view on this.
At times it can seem a little harsh but also I do absolutely get the logic behind it and that maybe it’s in thier best interests long term to be able to analyse and describe issues in the world of web dev because if you can’t describe it you can’t google it.
I think there’s probably no right or wrong answer, just different interpretations
Right. Talking about code is a critical skill. My thinking on this is twofold:
Software is typically developed in teams. Learning about how to talk to other developers is a skill that takes practice, so its important to start early.
Not all problems are obvious. You get better help and faster help when you can describe what you need help with.
When someone doesn’t include a description of their issue, I always include the message above, but if its obvious at a quick scan, I’ll also include my assessment of what the problem is.