“It’s not working” is not helpful
When someone asks a question about a problem with their code, we need to know what is wrong with it. Stating that “it doesn’t work” is not helpful.
Why this is a problem
In order to provide a solution, we need a full description of the problem. That includes
- What you are trying to accomplish
- What you have tried (including a minimal, complete, and verifiable example)
- A description of what the code did
- A description of why this does not achieve your goal
“It didn’t work” is not an adequate description for points 3 and/or 4.
Why this is worth a downvote
When one of these items is not provided, answerers have to guess what the missing pieces are. That increases the chances that their answers are incorrect, which is a waste of everyone’s time. Without enough information to answer a question, experienced users are less likely to attempt to answer, and more likely to downvote.
What to do next
Review your question. Did you provide a full description of what the code did? Did you point out the reasons why this result was not correct? Use the edit link at the bottom of your question (do not add a comment!) to provide these details. If commenters have asked pointed questions about what happened and why it wasn’t correct, make sure to address these questions directly.
If you do not know why your code did not work, that suggests you have not debugged it. Debugging is one of the first steps developers take when their code fails, and is an important skill to learn. Not debugging your code is also worth a downvote. To learn why, and for hints on how to debug your code, see our “No Debugging” page.
Leave a comment!
Once you have done this, leave a comment to the person who sent you this link. They will be happy to retract their downvote.
Did this page help you?
This website is here for everyone’s benefit, most importantly yours! If this did not help you, or if you would like to leave feedback, please create an Issue regarding this page on GitHub, or submit an improvement directly.