Asking questions about practical, concrete problems you have is one of the core principles of the StackExchange Q&A sites. So if you are in a situation where you can't recognize a good answer, you are probably asking the wrong kind of questions, i.e. questions which are not related to a real problem you got and you want/need to solve, which means you can't easily implement the answers you get, try to solve your problem and check either they are correct or not.

The accepting rate is a hint for other contributors to let them know if you are seriously considering the answers or not. Of course, it's not a perfect system: it's possible you get answers to a question, but none is satisfactory, which will drop your accepting rate. But usually, you get good answers, so if you don't accept any, it means your question is not really important to you and you are just wasting everybody's time.

So just keep focused on your real problems, and collective knowledge will emerge. That's Stack Overflow's magic!

Asking questions about practical, concrete problems you have is one of the core principles of the StackExchange Q&A sites. So if you are in a situation where you can't recognize a good answer, you are probably asking the wrong kind of questions, i.e. questions which are not related to a real problem you got and you want/need to solve, which means you can't easily implement the answers you get, try to solve your problem and check either the answers are correct or not.

The accepting rate is a hint for other contributors to let them know if you are seriously considering the answers or not. Of course, it's not a perfect system: it's possible you get answers to a question, but none is satisfactory, which will drop your accepting rate. But usually, you get good answers, so if you don't accept any, it means your question is not really important to you and you are just wasting everybody's time.

So just keep focused on your real problems, and collective knowledge will emerge. That's Stack Overflow's magic!

Asking questions about practical, concrete problems you have is one of the core principles of the StackExchange Q&A sites. So if you are in a situation where you can't recognize a good answer, you are probably asking the wrong kind of questions, i.e. questions which are not related to a real problem you got and you want/need to solve, which means you can't easily implement the answers you get, try to solve your problem and check either they are correct or not.

So just keep focused on your real problems, and collective knowledge will emerge. That's Stack Overflow's magic!

Asking questions about practical, concrete problems you have is one of the core principles of the StackExchange Q&A sites. So if you are in a situation where you can't recognize a good answer, you are probably asking the wrong kind of questions, i.e. questions which are not related to a real problem you got and you want/need to solve, which means you can't easily implement the answers you get, try to solve your problem and check either they are correct or not.

The accepting rate is a hint for other contributors to let them know if you are seriously considering the answers or not. Of course, it's not a perfect system: it's possible you get answers to a question, but none is satisfactory, which will drop your accepting rate. But usually, you get good answers, so if you don't accept any, it means your question is not really important to you and you are just wasting everybody's time.

So just keep focused on your real problems, and collective knowledge will emerge. That's Stack Overflow's magic!