Skip to main content
added 19 characters in body
Source Link
ChrisW
  • 13.1k
  • 14
  • 21

Instead of one artificial question with several carefully-crafted answers, you could:

  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific tag wiki, as suggested in 200_success's and rolfl's answer.

Example of answer titles/topics for one language (C#):

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...

Instead of one artificial question with several carefully-crafted answers, you could:

  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific tag wiki as suggested in rolfl's answer.

Example of answer titles/topics for one language (C#):

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...

Instead of one artificial question with several carefully-crafted answers, you could:

  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific tag wiki, as suggested in 200_success's and rolfl's answer.

Example of answer titles/topics for one language (C#):

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...
deleted 140 characters in body
Source Link
ChrisW
  • 13.1k
  • 14
  • 21

Instead of one artificial question with several carefully-crafted answers, you could:

  1. First:
  • Create a single "Canonical answers" post on Meta
  • Make it Community Wiki
  • Create a separate initially-empty answer for each language
  1. Then:
  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific meta-answertag wiki as suggested in rolfl's answer.

Example of a meta CW answer titles/topics for one language (C#):

C#

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...

Instead of one artificial question with several carefully-crafted answers, you could:

  1. First:
  • Create a single "Canonical answers" post on Meta
  • Make it Community Wiki
  • Create a separate initially-empty answer for each language
  1. Then:
  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific meta-answer

Example of a meta CW answer for one language:

C#

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...

Instead of one artificial question with several carefully-crafted answers, you could:

  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific tag wiki as suggested in rolfl's answer.

Example of answer titles/topics for one language (C#):

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...
Source Link
ChrisW
  • 13.1k
  • 14
  • 21

Instead of one artificial question with several carefully-crafted answers, you could:

  1. First:
  • Create a single "Canonical answers" post on Meta
  • Make it Community Wiki
  • Create a separate initially-empty answer for each language
  1. Then:
  • Wait until a real question is posted with one of these "common, core issues"
  • Post a carefully-crafted answer which addresses one issue
  • Add a link to your answer, to the corresponding language-specific meta-answer

Example of a meta CW answer for one language:

C#

  • Use using to Dispose disposable local variables <-- hyperlink
  • Make your class IDisposable to Dispose disposable instance data <-- hyperlink
  • ... etc ...