Return to Question

• language-agnostic - the question isn't related to a particular programming language but rather more a meta information regarding API usage, e.g. How to get the count of a query efficiently.
  => NO

• cross-language - the question will benefit from answers with code snippets per programming language, e.g. How to format reputation numbers similar to Stack Exchange sites.
  => MAYBE

  • I'm not entirely sure about this one, I'd appreciate the semantics outlined above but for some reason the tag has only been used 13 times on SO so far, maybe there is something better I'm not aware of right now?

• language-agnostic - the question isn't related to a particular programming language but rather more a meta information regarding API usage, e.g. How to get the count of a query efficiently.
  => NO

• cross-language - the question will benefit from answers with code snippets per programming language, e.g. How to format reputation numbers similar to Stack Exchange sites.
  => MAYBE

  • I'm not entirely sure about this one, I'd appreciate the semantics outlined above but for some reason the tag has only been used 13 times on SO so far, maybe there is something better I'm not aware of right now?

I've 'averaged' the few answers and comments and included the respective result below each question (all results are executed accordingly for some time already in most dev-tip posts). The empirical base here is obviously quite low, but so is the activity on Stack Apps in general still, hence this should do for now and can be updated/adjusted as needed.

I really like the approach code poet has taken with his dev-tip series and would like to see this evolve into a developer recipe like cookbook kinda thing/HOWTO/FAQ. However, if I look at the list of questions tagged dev-tip several questions pop up immediately. So I'd like to open a short discussion on the following early on, assuming this is a good time to refine the format without triggering to many change requirements; please consider each question as a separate topic in principle:

• language-agnostic - the question isn't related to a particular programming language but rather more a meta information regarding API usage, e.g. How to get the count of a query efficiently.
  => NO

• cross-language - the question will benefit from answers with code snippets per programming language, e.g. How to format reputation numbers similar to Stack Exchange sites.
  => MAYBE

  • I'm not entirely sure about this one, I'd appreciate the semantics outlined above but for some reason the tag has only been used 13 times on SO so far, maybe there is something better I'm not aware of right now?

4. Should we drop the 'dev-tip' tag? [added from code poets answer]
   => NO

• I agree with code poets reasoning here to keep it because this communicates the initial intent of the post being guidance, see his answer for details.

I've 'averaged' the few answers and comments and included the respective result below each question (all results are executed accordingly for some time already in most dev-tip posts). The empirical base here is obviously quite low, but so is the activity on Stack Apps in general still, hence this should do for now and can be updated/adjusted as needed.

I really like the approach code poet has taken with his dev-tip series and would like to see this evolve into a developer recipe like cookbook kinda thing/HOWTO/FAQ. However, if I look at the list of questions tagged dev-tip several questions pop up immediately. So I'd like to open a short discussion on the following early on, assuming this is a good time to refine the format without triggering to many change requirements; please consider each question as a separate topic in principle:

• language-agnostic - the question isn't related to a particular programming language but rather more a meta information regarding API usage, e.g. How to get the count of a query efficiently.
  => NO

• cross-language - the question will benefit from answers with code snippets per programming language, e.g. How to format reputation numbers similar to Stack Exchange sites.
  => MAYBE

  • I'm not entirely sure about this one, I'd appreciate the semantics outlined above but for some reason the tag has only been used 13 times on SO so far, maybe there is something better I'm not aware of right now?

4. Should we drop the 'dev-tip' tag? [added from code poets answer]
   => NO

• I agree with code poets reasoning here to keep it because this communicates the initial intent of the post being guidance, see his answer for details.

• I'm aware and in favor of the community wiki concept in general and think this would make sense for the question immediately indeed. However, this would turn all answers into cwiki automatically too, which wouldn't properly honor/motivate the effort put into posting a code snippet for another programming language for example. So this is a bit difficult - I'm not into the respective meta discussions, couldn't this get sorted over time, i.e. use cwiki automatically/voluntarily for the moment and see how it evolves?

• I'm aware and in favor of the community wiki concept in general and think this would make sense for the question immediately indeed. However, this would turn all answers into cwiki automatically too, which wouldn't properly honor/motivate the effort put into posting a code snippet for another programming language for example. So this is a bit difficult - I'm not into the respective meta discussions, couldn't this get sorted over time, i.e. use cwiki automatically/voluntarily for the moment and see how it evolves?