In fact, if you're asking on a forum about how to solve X, be sure to add "because A, B, C" or you're just wasting everyone else's fucking time. The more details you put up front, the more apt you're going to get the answer you're looking for in the first place instead of wasting everyone elses time of exploring the problem space.
you sure you're not the one wasting people's time by demanding they convince you of something you don't have any need to be convinced of - like did you know that just answering a question at face value is a completely plausible option?
Funny term to use as it has a very particular meaning of something that cannot/should not be interpreted because it is well defined.
This is a common flaw of the programmer type, especially when they go about writing code and documentation. That is, that what they are writing can only be interpreted in one way.
Then they toss it out into the real world and it turns out every human has a different interpretation, the runtime operates differently based on the phase of the moon, and even the compiler seems to be making its own best guess based on undefined behavior.
The value of int is typically well defined, but once you start stacking up these well defined bits, subjectivity quickly takes over.
> 3. Figurative Usage ("Taking at face value")When used in everyday language as a phrase, "taking something at face value" means accepting a statement, situation, or person exactly as they appear or are presented, without digging deeper for hidden meanings, motives, or questioning their authenticity
...
not sure what version of the english language you're using but in colloquial english "taking something at face value" means having a good faith interpretation.
The fact you're complaining about the this, rather than modifying your own behaviour in a way that improves people's chances of helping you, seems quite extraordinary.
