Post History
The key to writing good self-answered Q&A is to try to write the question just as if you didn't know the answer. That is, it has to fulfil the usual quality criteria for normal questions. This ...
Answer
#2: Post edited
- The key to writing good self-answered Q&A is to try to write the question just as if you didn't know the answer. That is, it has to fulfil the usual quality criteria for normal questions. This can be quite hard!
- My best advise is probably to give a specific example in the question. For example post a schematic even if it is incomplete or contains obvious errors - those are the parts you supposedly need help with. Answers can then correct the circuit as part of the explanation.
- Ideally, such questions should contain common newbie mistakes relevant to the question. That makes the question a strong candidate for a "canonical duplicate" that we can use as a "close as duplicate of" target whenever newbies ask FAQ about that matter.
- For example if you are posting a question regarding how to read and de-bounce a mechanical switch by using passives, you might post a schematic containing nothing but +5V, a switch symbol and maybe a MCU input pin.
Answers can then address issues like missing pull resistor, intended polarity, how to add a RC filter, ESD issues and so on. And together with the explanation illustrate by posting a corrected schematic. Some explanation about RC low pass filter theory & formula can be accompanied with examples of suitable values, and so on.
- The key to writing good self-answered Q&A is to try to write the question just as if you didn't know the answer. That is, it has to fulfil the usual quality criteria for normal questions. This can be quite hard!
- My best advise is probably to give a specific example in the question. For example post a schematic even if it is incomplete or contains obvious errors - those are the parts you supposedly need help with. Answers can then correct the circuit as part of the explanation.
- Ideally, such questions should contain common newbie mistakes relevant to the question. That makes the question a strong candidate for a "canonical duplicate" that we can use as a "close as duplicate of" target whenever newbies ask FAQ about that matter.
- For example if you are posting a question regarding how to read and de-bounce a mechanical switch by using passives, you might post a schematic containing nothing but +5V, a switch symbol and maybe a MCU input pin.
- Answers can then address issues like missing pull resistor, intended polarity, how to add a RC filter, ESD issues etc. And together with the explanation illustrate by posting a corrected schematic. Some explanation about RC low pass filter theory & formula can be accompanied with examples of suitable values, and so on.
#1: Initial revision
The key to writing good self-answered Q&A is to try to write the question just as if you didn't know the answer. That is, it has to fulfil the usual quality criteria for normal questions. This can be quite hard! My best advise is probably to give a specific example in the question. For example post a schematic even if it is incomplete or contains obvious errors - those are the parts you supposedly need help with. Answers can then correct the circuit as part of the explanation. Ideally, such questions should contain common newbie mistakes relevant to the question. That makes the question a strong candidate for a "canonical duplicate" that we can use as a "close as duplicate of" target whenever newbies ask FAQ about that matter. For example if you are posting a question regarding how to read and de-bounce a mechanical switch by using passives, you might post a schematic containing nothing but +5V, a switch symbol and maybe a MCU input pin. Answers can then address issues like missing pull resistor, intended polarity, how to add a RC filter, ESD issues and so on. And together with the explanation illustrate by posting a corrected schematic. Some explanation about RC low pass filter theory & formula can be accompanied with examples of suitable values, and so on.