Skip to main content
replaced http://superuser.com/ with https://superuser.com/
Source Link

Frontload your questions. For heaven's sake, don't start your questions with "Hi guys, I'm new here, and I don't know much about SQL but I was wondering ..."

Instead jump right into either an easy to grasp description of the problem that led to your question, or a precise nailing down of your question. If possible, the title should be a condensed version of the question in your first paragraph, one that attracts people who have the right kind of knowledge to help you.

The most common edits I perform on other people's questions are (i) making the title reflect what the questioner actually wants, and (ii) removing introductory fluff.

Two resources:

  1. quack quixote's analysis of what was wrong with an SU question of minean SU question of mine got me to think harder about what kind of questions were good for potential answerers;
  2. Frontloading is a bit like Wikipedia's summary style.

Frontload your questions. For heaven's sake, don't start your questions with "Hi guys, I'm new here, and I don't know much about SQL but I was wondering ..."

Instead jump right into either an easy to grasp description of the problem that led to your question, or a precise nailing down of your question. If possible, the title should be a condensed version of the question in your first paragraph, one that attracts people who have the right kind of knowledge to help you.

The most common edits I perform on other people's questions are (i) making the title reflect what the questioner actually wants, and (ii) removing introductory fluff.

Two resources:

  1. quack quixote's analysis of what was wrong with an SU question of mine got me to think harder about what kind of questions were good for potential answerers;
  2. Frontloading is a bit like Wikipedia's summary style.

Frontload your questions. For heaven's sake, don't start your questions with "Hi guys, I'm new here, and I don't know much about SQL but I was wondering ..."

Instead jump right into either an easy to grasp description of the problem that led to your question, or a precise nailing down of your question. If possible, the title should be a condensed version of the question in your first paragraph, one that attracts people who have the right kind of knowledge to help you.

The most common edits I perform on other people's questions are (i) making the title reflect what the questioner actually wants, and (ii) removing introductory fluff.

Two resources:

  1. quack quixote's analysis of what was wrong with an SU question of mine got me to think harder about what kind of questions were good for potential answerers;
  2. Frontloading is a bit like Wikipedia's summary style.
Post Migrated Here from meta.stackexchange.com (revisions)
Post Made Community Wiki
Source Link
Charles Stewart
Charles Stewart

Frontload your questions. For heaven's sake, don't start your questions with "Hi guys, I'm new here, and I don't know much about SQL but I was wondering ..."

Instead jump right into either an easy to grasp description of the problem that led to your question, or a precise nailing down of your question. If possible, the title should be a condensed version of the question in your first paragraph, one that attracts people who have the right kind of knowledge to help you.

The most common edits I perform on other people's questions are (i) making the title reflect what the questioner actually wants, and (ii) removing introductory fluff.

Two resources:

  1. quack quixote's analysis of what was wrong with an SU question of mine got me to think harder about what kind of questions were good for potential answerers;
  2. Frontloading is a bit like Wikipedia's summary style.