Looking at your questions, they are not all straightforward to reproduce. It is not just a matter of expertise. I may be wrong as I don't know about all these topics, but to me only the first one looks simple to reproduce:

• Why does typedef struct produce a link failure
• How to get NetBeans 7.4, Ruby and MySQL to play together (on Windows)
• How to diff/merge changes in stages, with automation
• Can an Android layout scale to fill the screen?
• Android NDK: How to get a Context from inside NDK code

The others would either require me to write a lot of code to reproduce the problem or to carefully set up an environment. Even if you were able to target your question at an expert, you are still asking them to do a lot of work.

I could try to write long questions explaining what I'm looking for, but from experience long questions are hard to read for busy people, and many of mine are really quite short.

Reading is not always hard work. Asking lots of clarifying questions is hard work though and these are often needed if a problem is not easy to reproduce. If a question looks like it will need lots of clarifying questions then I am likely to avoid answering it (not laying claim to expert status on anything here).

My experience on SO is that writing a long question including a minimal example results in good answers.

Looking at your questions, they are not all straightforward to reproduce. It is not just a matter of expertise. I may be wrong as I don't know about all these topics, but to me only the first one looks simple to reproduce:

• Why does typedef struct produce a link failure
• How to get NetBeans 7.4, Ruby and MySQL to play together (on Windows)
• How to diff/merge changes in stages, with automation
• Can an Android layout scale to fill the screen?
• Android NDK: How to get a Context from inside NDK code

The others would either require me to write a lot of code to reproduce the problem or to carefully set up an environment. Even if you were able to target your question at an expert, you are still asking them to do a lot of work.

I could try to write long questions explaining what I'm looking for, but from experience long questions are hard to read for busy people, and many of mine are really quite short.

Reading is not always hard work. Asking lots of clarifying questions is hard work though and these are often needed if a problem is not easy to reproduce. If a question looks like it will need lots of clarifying questions then I am likely to avoid answering it (not laying claim to expert status on anything here).

My experience on SO is that writing a long question including a minimal example results in good answers.

Looking at your questions, they are not all straightforward to reproduce. It is not just a matter of expertise. I may be wrong as I don't know about all these topics, but to me only the first one looks simple to reproduce:

• Why does typedef struct produce a link failure
• How to get NetBeans 7.4, Ruby and MySQL to play together (on Windows)
• How to diff/merge changes in stages, with automation
• Can an Android layout scale to fill the screen?
• Android NDK: How to get a Context from inside NDK code

The others would either require me to write a lot of code to reproduce the problem or to carefully set up an environment. Even if you were able to target your question at an expert, you are still asking them to do a lot of work.

I could try to write long questions explaining what I'm looking for, but from experience long questions are hard to read for busy people, and many of mine are really quite short.

Reading is not always hard work. Asking lots of clarifying questions is hard work though. If a question looks like it will need lots of clarifying questions then I am likely to avoid answering it (not laying claim to expert status on anything here).

My experience on SO is that writing a long question including a minimal example results in good answers.

Looking at your questions, they are not all straightforward to reproduce. It is not just a matter of expertise. I may be wrong as I don't know about all these topics, but to me only the first one looks simple to reproduce:

• Why does typedef struct produce a link failure
• How to get NetBeans 7.4, Ruby and MySQL to play together (on Windows)
• How to diff/merge changes in stages, with automation
• Can an Android layout scale to fill the screen?
• Android NDK: How to get a Context from inside NDK code

The others would either require me to write a lot of code to reproduce the problem or to carefully set up an environment. Even if you were able to target your question at an expert, you are still asking them to do a lot of work.

I could try to write long questions explaining what I'm looking for, but from experience long questions are hard to read for busy people, and many of mine are really quite short.

Reading is not always hard work. Asking lots of clarifying questions is hard work though and these are often needed if a problem is not easy to reproduce. If a question looks like it will need lots of clarifying questions then I am likely to avoid answering it (not laying claim to expert status on anything here).

My experience on SO is that writing a long question including a minimal example results in good answers.