Jan-25-2017, 03:06 AM
how should one post without code?
is it valid to ask a question without including any code?
what if i want to just understand the general meaning of an error message?
when i run into an error in a program i often get an error message. the other major error result is incorrect output. another is that the program does nothing. if i did get an error message the (approximately) first thing i do is try to understand what the error message means. most of the time it is a syntax error. my most common mistake is forgetting a trailing ) from the previous line. so i usually need to get the line number from the traceback and look there or the line above.
but in rare cases i don't understand the error message. why can't i just ask about that without the code?
it is common for us to want to see minimal code. but these would be questions along the lines of why does my code failat that? seeing the code helps.
minimizing the code helps. it also helps debugging. i have a funny story about that from days long ago which i may post later.
but i want to at least try to understand each step along the way. dealing with, or getting the most information from, the error message is one of the first.
i don't like long code. if someone posts a question asking why their code failed, and code is long, i usually just skip over it. if i were a moderator, i might have to do something, but i am not. this is why minimized code is better. since it is usually a good debugging process, it should be done, anyway. that gets us into the mindset "post the (minimal) code"
i just want to understand if we always need to post code here. maybe that "post the (minimal) code" mindset has blurred us into thinking we need to see the code more often.
is it valid to ask a question without including any code?
what if i want to just understand the general meaning of an error message?
when i run into an error in a program i often get an error message. the other major error result is incorrect output. another is that the program does nothing. if i did get an error message the (approximately) first thing i do is try to understand what the error message means. most of the time it is a syntax error. my most common mistake is forgetting a trailing ) from the previous line. so i usually need to get the line number from the traceback and look there or the line above.
but in rare cases i don't understand the error message. why can't i just ask about that without the code?
it is common for us to want to see minimal code. but these would be questions along the lines of why does my code failat that? seeing the code helps.
minimizing the code helps. it also helps debugging. i have a funny story about that from days long ago which i may post later.
but i want to at least try to understand each step along the way. dealing with, or getting the most information from, the error message is one of the first.
i don't like long code. if someone posts a question asking why their code failed, and code is long, i usually just skip over it. if i were a moderator, i might have to do something, but i am not. this is why minimized code is better. since it is usually a good debugging process, it should be done, anyway. that gets us into the mindset "post the (minimal) code"
i just want to understand if we always need to post code here. maybe that "post the (minimal) code" mindset has blurred us into thinking we need to see the code more often.