Return to Answer

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it. By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. However, it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help on a list of requirements is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it (especially if some requirements are unclear or poorly scoped). By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. However, it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it. By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. Although, it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it. By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. However, it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it. By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. Although it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!

Stack Overflow is a question & answer site. You may think that you have asked a reasonable, answerable question, but a question like "Can someone help me"? really doesn't qualify.

First, a bit of background: The purpose of Stack Overflow is to create a knowledge repository of solutions to programming problems. Its mantra is "Make the Internet a better place". That means that a primary characteristic of a good question is that it is likely to be searched by someone else. "Will you help me do X?" doesn't do that. More than likely, no one will ever be trying to do, and searching for, the exact same thing as you in exactly the same way. On the other hand, questions like: "How do I convert a string to a number?" are searched very often.

Second, for the sake of argument, suppose we didn't care whether the question is useful to someone else (we do), that we are only here for you (we aren't). A request for help is still impossible to answer. Imagine what an answer might look like. It would essentially need to be the entire code base. We can appreciate that you only want "help", but with the question you've asked, we can't provide it. By contrast, something like "How do I convert a string to a number?" has a clear definable answer (or even multiple answers).

So, help us help you. When you write a question, make sure to actually ask a question. Answerable questions don't ask how to implement a feature, they ask how to accomplish a programming task (among other things).

There's a catch here, that asking a good question will nearly always require you to know enough to know what you don't know. If you aren't there yet, start by breaking down the problem/feature into as many small steps as you can, and ask about the ones you don't understand and can't answer by doing your own research. Although, it still helps to mention the context, just in case you're approaching the problem from the wrong angle.

So in summary:

• Ask one question per post.
• Make sure it is clear what you want to know. Is the question about fixing existing code, or is it about figuring out the next part of the code? Either way, what specifically do you need to understand in order to solve the problem?
• Ask a specific programming question, not how to implement an entire project or feature.
• If you don't know the programming question to ask, at least break it down into as small a piece as possible, and still make it about programming, not the feature.
  • If you are trying to figure out how to do something, then think about what things need to happen and in what order, figure out what you can and can't do already, and focus on a step that causes a problem.
  • If you are trying to fix a problem in code, then try to check what each part of the code does separately, figure out what part is doing something wrong, and ask about that with a minimal reproducible example.
• Wait for the reaction you get and think about it before asking the next question you may have. It might already be obsolete or just change radically.

The good news is, you are trying to learn. So work on the question, edit it into something answerable, or at least make sure your next question is a good one. We'll be glad to help!