Timeline for 'Canonical' questions to help address common issues
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:09 | history | edited | CommunityBot |
Commonmark migration
|
|
| May 1, 2018 at 20:46 | comment | added | JDługosz | My problem with simply pointing back to a previous (normal) answer post is that it is not single-topic. That guy's review will have all kinds of stuff. The artificial exemplar question would have perhaps one line of code. | |
| Apr 13, 2017 at 12:41 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
|
|
| Mar 26, 2014 at 12:30 | comment | added | Mathieu Guindon | MSDN would be the "last word" on the subject, that people can link to now and in the future... | |
| Mar 26, 2014 at 10:23 | comment | added | ChrisW | ... this and camelCase for that; mentions why conventions are important; suggest tools for doing static analysis of style; add a hyperlink to the document in which these conventions are defined.` | |
| Mar 26, 2014 at 10:22 | comment | added | ChrisW | @Corbin You can try to create a 'canonical answer', which for example: a) can address a single topic/problem (not every problem in that piece of code b) name the topic/problem well c) explain the problem in detail and also try to explain it in general d) contain hyperlinks to canonical references e) therefore be an exemplary answer or 'the last word' on the subject, which other people will want to link to in future, and which therefore deserves to be added to the tag wiki. For example `## Use standard casing conventions for identifiers\n\n(Explains that the language uses Pascal case for ... | |
| Mar 26, 2014 at 3:53 | comment | added | Mathieu Guindon | I suppose we could have links to frequently linked-to answers in a language's tag wiki... maintained by whoever finds a good answer to link to. | |
| Mar 26, 2014 at 3:49 | comment | added | Corbin | The more I think about it, the more I think CW is a bad idea. At the end of the day, we all like and need (from a beta perspective) rep. I am a bit confused though: are you saying a central repository is a bad idea period, or that a central repo should just link to personal answers (like have the language wiki have a bunch of links to exemplary answers)? (Basically have a community curated list of links rather than a community curated set of content?) | |
| Mar 26, 2014 at 2:42 | history | answered | Mathieu Guindon | CC BY-SA 3.0 |