Skip to main content

Return to Answer

added 108 characters in body
Source Link
CodeCaster
CodeCaster
  • 152.6k
  • 35
  • 190
  • 314

You know, I kindakind of like the "recommended answer" part, but I can see it going wrong, fast.

The reason I like it, is that I've been looking forfantasizing about a way to highlight quality answers for a while. I have thought about proposing a review system, in the sense of established users properly reviewing a post on points like readability, applicability, compatibility, security, correctness, maintainability and so on. Something more than just up- and downvotes.

This "seal of approval" does that in a very basic way: it gives a visible "trusted +1", so to say. But just as with votes, you'll have to look out for the abrupt devaluation of this seal.

Or: who trusts the trusters?

If, for example, a given collective mass-employs recognized members who in turn approve any answer that even remotely seems to answer the question, then it's borked by design. It'll become equivalent to the decades-old Microsoft forums joke (there's a tautology in there somewhere):

  • User posts a question
  • Moderator / independent contractor / power user posts their default boilerplate canned answer they post to every frigging question that hits a certain keyword ("Try running system restore, don't forget to like and subscribe")
  • User has seen this before and gives up, sometimes tries responding which is usually ignored
  • Moderator returns after a few days, marks thread as inactive, marks their own answer as best

You don't want that seal to hold that little value, now do you?

So how can a company manage all questions in a tag as large as Go, let alone Java or C# or JavaScript (and who can manage the latter)? Is the UI efficient to filter and sort through new and existing questions and answers? Is someone (Stack Overflow staff, moderators, users) watching what those collectives and their members do, now and in the near and far future? What about duplicate questions that are still open, and duplicate answers where some or all of them receive a seal? Can users flag a marked post to tell a moderator, or the collective's users (or both) that the answer shouldn't be sealed, as it's promoting a bad practice or incorrect?

You know, I kinda like the "recommended answer" part.

I've been looking for a way to highlight quality answers for a while. I have thought about proposing a review system, in the sense of established users properly reviewing a post on points like readability, applicability, compatibility, security, correctness, maintainability and so on. Something more than just up- and downvotes.

This "seal of approval" does that in a very basic way: it gives a visible "trusted +1", so to say. But just as with votes, you'll have to look out for the abrupt devaluation of this seal.

If, for example, a given collective mass-employs recognized members who in turn approve any answer that even remotely seems to answer the question, then it's borked by design. It'll become equivalent to the decades-old Microsoft forums joke (there's a tautology in there somewhere):

  • User posts a question
  • Moderator / independent contractor / power user posts their default boilerplate canned answer they post to every frigging question that hits a certain keyword ("Try running system restore, don't forget to like and subscribe")
  • User has seen this before and gives up, sometimes tries responding which is usually ignored
  • Moderator returns after a few days, marks thread as inactive, marks their own answer as best

You don't want that seal to hold that little value, now do you?

So how can a company manage all questions in a tag as large as Go, let alone Java or C# or JavaScript (and who can manage the latter)? Is the UI efficient to filter and sort through new and existing questions and answers? Is someone (Stack Overflow staff, moderators, users) watching what those collectives and their members do, now and in the near and far future? What about duplicate questions that are still open, and duplicate answers where some or all of them receive a seal? Can users flag a marked post to tell a moderator, or the collective's users (or both) that the answer shouldn't be sealed, as it's promoting a bad practice or incorrect?

You know, I kind of like the "recommended answer" part, but I can see it going wrong, fast.

The reason I like it, is that I've been fantasizing about a way to highlight quality answers for a while. I have thought about proposing a review system, in the sense of established users properly reviewing a post on points like readability, applicability, compatibility, security, correctness, maintainability and so on. Something more than just up- and downvotes.

This "seal of approval" does that in a very basic way: it gives a visible "trusted +1", so to say. But just as with votes, you'll have to look out for the abrupt devaluation of this seal.

Or: who trusts the trusters?

If, for example, a given collective mass-employs recognized members who in turn approve any answer that even remotely seems to answer the question, then it's borked by design. It'll become equivalent to the decades-old Microsoft forums joke (there's a tautology in there somewhere):

  • User posts a question
  • Moderator / independent contractor / power user posts their default boilerplate canned answer they post to every frigging question that hits a certain keyword ("Try running system restore, don't forget to like and subscribe")
  • User has seen this before and gives up, sometimes tries responding which is usually ignored
  • Moderator returns after a few days, marks thread as inactive, marks their own answer as best

You don't want that seal to hold that little value, now do you?

So how can a company manage all questions in a tag as large as Go, let alone Java or C# or JavaScript (and who can manage the latter)? Is the UI efficient to filter and sort through new and existing questions and answers? Is someone (Stack Overflow staff, moderators, users) watching what those collectives and their members do, now and in the near and far future? What about duplicate questions that are still open, and duplicate answers where some or all of them receive a seal? Can users flag a marked post to tell a moderator, or the collective's users (or both) that the answer shouldn't be sealed, as it's promoting a bad practice or incorrect?

Source Link
CodeCaster
CodeCaster
  • 152.6k
  • 35
  • 190
  • 314

You know, I kinda like the "recommended answer" part.

I've been looking for a way to highlight quality answers for a while. I have thought about proposing a review system, in the sense of established users properly reviewing a post on points like readability, applicability, compatibility, security, correctness, maintainability and so on. Something more than just up- and downvotes.

This "seal of approval" does that in a very basic way: it gives a visible "trusted +1", so to say. But just as with votes, you'll have to look out for the abrupt devaluation of this seal.

If, for example, a given collective mass-employs recognized members who in turn approve any answer that even remotely seems to answer the question, then it's borked by design. It'll become equivalent to the decades-old Microsoft forums joke (there's a tautology in there somewhere):

  • User posts a question
  • Moderator / independent contractor / power user posts their default boilerplate canned answer they post to every frigging question that hits a certain keyword ("Try running system restore, don't forget to like and subscribe")
  • User has seen this before and gives up, sometimes tries responding which is usually ignored
  • Moderator returns after a few days, marks thread as inactive, marks their own answer as best

You don't want that seal to hold that little value, now do you?

So how can a company manage all questions in a tag as large as Go, let alone Java or C# or JavaScript (and who can manage the latter)? Is the UI efficient to filter and sort through new and existing questions and answers? Is someone (Stack Overflow staff, moderators, users) watching what those collectives and their members do, now and in the near and far future? What about duplicate questions that are still open, and duplicate answers where some or all of them receive a seal? Can users flag a marked post to tell a moderator, or the collective's users (or both) that the answer shouldn't be sealed, as it's promoting a bad practice or incorrect?