|
> I read the answer of that “duplicate” and it was not applicable to my problem You are supposed to have a question in the first place, not just a problem. (In fact, you are not required to have had anything go wrong with your code, nor to need to know how to do something, in order to ask a question. You only need to ask a question that meets standards.) If something was wrong with your code, and using Stack Overflow didn't enable you to fix the code, that is not Stack Overflow's concern, by design. If you expect that your interaction with a website will enable you to fix broken code that you have, and the only standard by which you judge the website is "did I end up fixing my broken code", then Stack Overflow is not the site you want. And that's fine. There are millions of other websites out there that will also not help you fix your broken code. Why should Stack Overflow be required to do so? Just because it's about programming and accepts user-generated content? (Did you know about https://wiki.python.org/moin/ , by the way?) If you analyzed some non-working code, and found a specific part that did something different from what you expected, and produced a MCVE (although we say https://stackoverflow.com/help/minimal-reproducible-example), then you have an acceptable question. Or if you figured out that you need to do something specific, and came up with a clear, precise specification for it, and there isn't a clear way to break the task down further into logical steps. And when that question gets closed as a duplicate, you can bet that the accuracy rate is pretty high. You should try the answer, adapting it back to your own MCVE / specification, and then back to the original context. |