19 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet can have a questionhave a question that is like a common canonical problem typea common canonical problem type but subtly, importantly different.

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet can have a question that is like a common canonical problem type but subtly, importantly different.

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet can have a question that is like a common canonical problem type but subtly, importantly different.

18 replaced http://travel.stackexchange.com/ with https://travel.stackexchange.com/
source | link

Let's use a recent example, where we have a great canonical resource on travelling with dual citizenshipa great canonical resource on travelling with dual citizenship, and someone has a delicate problem where it'll be very difficult for them to do what the canonical answer suggestsa delicate problem where it'll be very difficult for them to do what the canonical answer suggests, where duping to the canonical question is like telling someone to read a (short, well-written) manual that doesn't actually even address the details of their specific problem.

Let's use a recent example, where we have a great canonical resource on travelling with dual citizenship, and someone has a delicate problem where it'll be very difficult for them to do what the canonical answer suggests, where duping to the canonical question is like telling someone to read a (short, well-written) manual that doesn't actually even address the details of their specific problem.

Let's use a recent example, where we have a great canonical resource on travelling with dual citizenship, and someone has a delicate problem where it'll be very difficult for them to do what the canonical answer suggests, where duping to the canonical question is like telling someone to read a (short, well-written) manual that doesn't actually even address the details of their specific problem.

17 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

From an older post from SE staff member shog9an older post from SE staff member shog9.

Shog9's first of several related reading linksof several related reading links expands on this a little with a quote from an official blog post. The examples are very programming specific but it's not hard to see how they relate:

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet#1 ranked user Jon Skeet can have a question that is like a common canonical problem type but subtly, importantly different.

From an older post from SE staff member shog9.

Shog9's first of several related reading links expands on this a little with a quote from an official blog post. The examples are very programming specific but it's not hard to see how they relate:

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet can have a question that is like a common canonical problem type but subtly, importantly different.

From an older post from SE staff member shog9.

Shog9's first of several related reading links expands on this a little with a quote from an official blog post. The examples are very programming specific but it's not hard to see how they relate:

Bloating the canonical to fit a case that it's pattern or technique doesn't currently fit would clearly risk heading towards the massive canonical Topic FAQ tomes that are warned against. There's nothing awkward or wrong about having edge cases that are like a common canonical pattern, but with circumstances different enough that this doesn't solve them. Even the SE network's #1 ranked user Jon Skeet can have a question that is like a common canonical problem type but subtly, importantly different.

16 replaced http://meta.scifi.stackexchange.com/ with https://scifi.meta.stackexchange.com/
source | link
15 replaced http://meta.travel.stackexchange.com/ with https://travel.meta.stackexchange.com/
source | link
14 added 124 characters in body
source | link
13 added 124 characters in body
source | link
12 added 124 characters in body
source | link
11 added 124 characters in body
source | link
10 deleted 562 characters in body
source | link
9 added 333 characters in body
source | link
8 added 333 characters in body
source | link
7 added 2838 characters in body
source | link
6 added 2838 characters in body
source | link
    Tweeted twitter.com/StackTravel/status/725016310728544256
5 added 150 characters in body
source | link
4 added 150 characters in body
source | link
3 added 387 characters in body
source | link
2 deleted 1 character in body
source | link
1
source | link