Skip to main content
Commonmark migration
Source Link

Aside from bringing this to meta is there anything else we can do to remind people to review with care?

No. And calling out specific users on Meta is not an appropriate course of action anyway.

As Makoto already said in the comments, if you see someone consistently making bad decisions about reviews, then raise a moderator flag on one of their posts. Use the textbox to provide your evidence, and then let one of us handle it. As a moderator on other Stack Exchange sites, you know that moderators have tools to see a user's review history, as well as tools to reach out to the user and/or put a stop to any further erroneous reviews.

Even though you, as a regular user, could leave a comment encouraging people to pay more attention when reviewing, it (A) just creates noise that has to be cleaned up eventually by a moderator, so you aren't saving us all that much work, and (B) rarely is as effective as when the message comes from a moderator. Besides, if there is real harm being done by the user's erroneous reviews, then a moderator needs to put a stop to any further "accidents"; a comment from you won't reach them in time, if it even works at all.


As far as using "Skip" goes…I agree wholeheartedly that the option is criminally under-used by reviewers, but…two things:

  1. As you (and gnat) already took great care to cite, we've made this announcement many times on Meta. The reviewers' failure to use it is not for the community's lack of trying. And contrary to certain other options, the review queue's design already makes "Skip" a pretty prominent, obvious choice.

    As you (and gnat) already took great care to cite, we've made this announcement many times on Meta. The reviewers' failure to use it is not for the community's lack of trying. And contrary to certain other options, the review queue's design already makes "Skip" a pretty prominent, obvious choice.

  2. I think it's a red herring in the case you cite (and very likely in others). Those reviewers who approved the edit weren't unsure, so even if they were "Skip" connoisseurs, they very likely would not have used it in this case. They felt sure that it was a good edit, because it was improving the question by adding code.

    I think it's a red herring in the case you cite (and very likely in others). Those reviewers who approved the edit weren't unsure, so even if they were "Skip" connoisseurs, they very likely would not have used it in this case. They felt sure that it was a good edit, because it was improving the question by adding code.

    In other words, this isn't a review that anyone needed to skip. It's just evidence of a basic lack of knowledge about which types of edits need to be approved and what information needs to be considered when making that decision. If you have ideas about how to better disseminate that knowledge, and/or how to generally improve the review queues, then you should post those as separate feature requests.

In other words, this isn't a review that anyone needed to skip. It's just evidence of a basic lack of knowledge about which types of edits need to be approved and what information needs to be considered when making that decision. If you have ideas about how to better disseminate that knowledge, and/or how to generally improve the review queues, then you should post those as separate feature requests.

Aside from bringing this to meta is there anything else we can do to remind people to review with care?

No. And calling out specific users on Meta is not an appropriate course of action anyway.

As Makoto already said in the comments, if you see someone consistently making bad decisions about reviews, then raise a moderator flag on one of their posts. Use the textbox to provide your evidence, and then let one of us handle it. As a moderator on other Stack Exchange sites, you know that moderators have tools to see a user's review history, as well as tools to reach out to the user and/or put a stop to any further erroneous reviews.

Even though you, as a regular user, could leave a comment encouraging people to pay more attention when reviewing, it (A) just creates noise that has to be cleaned up eventually by a moderator, so you aren't saving us all that much work, and (B) rarely is as effective as when the message comes from a moderator. Besides, if there is real harm being done by the user's erroneous reviews, then a moderator needs to put a stop to any further "accidents"; a comment from you won't reach them in time, if it even works at all.


As far as using "Skip" goes…I agree wholeheartedly that the option is criminally under-used by reviewers, but…two things:

  1. As you (and gnat) already took great care to cite, we've made this announcement many times on Meta. The reviewers' failure to use it is not for the community's lack of trying. And contrary to certain other options, the review queue's design already makes "Skip" a pretty prominent, obvious choice.
  2. I think it's a red herring in the case you cite (and very likely in others). Those reviewers who approved the edit weren't unsure, so even if they were "Skip" connoisseurs, they very likely would not have used it in this case. They felt sure that it was a good edit, because it was improving the question by adding code.

In other words, this isn't a review that anyone needed to skip. It's just evidence of a basic lack of knowledge about which types of edits need to be approved and what information needs to be considered when making that decision. If you have ideas about how to better disseminate that knowledge, and/or how to generally improve the review queues, then you should post those as separate feature requests.

Aside from bringing this to meta is there anything else we can do to remind people to review with care?

No. And calling out specific users on Meta is not an appropriate course of action anyway.

As Makoto already said in the comments, if you see someone consistently making bad decisions about reviews, then raise a moderator flag on one of their posts. Use the textbox to provide your evidence, and then let one of us handle it. As a moderator on other Stack Exchange sites, you know that moderators have tools to see a user's review history, as well as tools to reach out to the user and/or put a stop to any further erroneous reviews.

Even though you, as a regular user, could leave a comment encouraging people to pay more attention when reviewing, it (A) just creates noise that has to be cleaned up eventually by a moderator, so you aren't saving us all that much work, and (B) rarely is as effective as when the message comes from a moderator. Besides, if there is real harm being done by the user's erroneous reviews, then a moderator needs to put a stop to any further "accidents"; a comment from you won't reach them in time, if it even works at all.


As far as using "Skip" goes…I agree wholeheartedly that the option is criminally under-used by reviewers, but…two things:

  1. As you (and gnat) already took great care to cite, we've made this announcement many times on Meta. The reviewers' failure to use it is not for the community's lack of trying. And contrary to certain other options, the review queue's design already makes "Skip" a pretty prominent, obvious choice.

  2. I think it's a red herring in the case you cite (and very likely in others). Those reviewers who approved the edit weren't unsure, so even if they were "Skip" connoisseurs, they very likely would not have used it in this case. They felt sure that it was a good edit, because it was improving the question by adding code.

    In other words, this isn't a review that anyone needed to skip. It's just evidence of a basic lack of knowledge about which types of edits need to be approved and what information needs to be considered when making that decision. If you have ideas about how to better disseminate that knowledge, and/or how to generally improve the review queues, then you should post those as separate feature requests.

Source Link
Cody Gray Mod
  • 246.2k
  • 85
  • 736
  • 777

Aside from bringing this to meta is there anything else we can do to remind people to review with care?

No. And calling out specific users on Meta is not an appropriate course of action anyway.

As Makoto already said in the comments, if you see someone consistently making bad decisions about reviews, then raise a moderator flag on one of their posts. Use the textbox to provide your evidence, and then let one of us handle it. As a moderator on other Stack Exchange sites, you know that moderators have tools to see a user's review history, as well as tools to reach out to the user and/or put a stop to any further erroneous reviews.

Even though you, as a regular user, could leave a comment encouraging people to pay more attention when reviewing, it (A) just creates noise that has to be cleaned up eventually by a moderator, so you aren't saving us all that much work, and (B) rarely is as effective as when the message comes from a moderator. Besides, if there is real harm being done by the user's erroneous reviews, then a moderator needs to put a stop to any further "accidents"; a comment from you won't reach them in time, if it even works at all.


As far as using "Skip" goes…I agree wholeheartedly that the option is criminally under-used by reviewers, but…two things:

  1. As you (and gnat) already took great care to cite, we've made this announcement many times on Meta. The reviewers' failure to use it is not for the community's lack of trying. And contrary to certain other options, the review queue's design already makes "Skip" a pretty prominent, obvious choice.
  2. I think it's a red herring in the case you cite (and very likely in others). Those reviewers who approved the edit weren't unsure, so even if they were "Skip" connoisseurs, they very likely would not have used it in this case. They felt sure that it was a good edit, because it was improving the question by adding code.

In other words, this isn't a review that anyone needed to skip. It's just evidence of a basic lack of knowledge about which types of edits need to be approved and what information needs to be considered when making that decision. If you have ideas about how to better disseminate that knowledge, and/or how to generally improve the review queues, then you should post those as separate feature requests.