Re:Conventional Comments
by graypegg on Saturday May 21, 2022 @07:11PM
(#31463041)
I like the concept, but this almost reaches into the realm of pedantic. I don’t think you really need more than “nitpick:” if you want to soften up your comment a bit. (At least don’t systematize into a list of tokens you have to police to keep things consistant)
Re:Conventional Comments
by jamessb on Sunday May 22, 2022 @09:29AM
(#31467967)
They criticise the comment: "This is not worded correctly.", by saying that "Comments like this are unhelpful… ", which is true.
However, I don't think that even their example of an "actionable" comment ("suggestion: This is not worded correctly. Can we change this to match the wording of the marketing page?") is actually a "good" comment, because whilst it is slightly more specific it still doesn't say what the wording on the marketing page actually is.
It would be better to write: "Can we change 'X' to 'Y' to match the wording of the marketing page?".
Re:Conventional Comments
by c0balt on Sunday May 22, 2022 @04:23AM
(#31466037)
I like the concept and employ some of it for personal use. A vscode extension[0] helped me getting started and now its used in nearly all of my projects.
However, I don't think that even their example of an "actionable" comment ("suggestion: This is not worded correctly. Can we change this to match the wording of the marketing page?") is actually a "good" comment, because whilst it is slightly more specific it still doesn't say what the wording on the marketing page actually is.
It would be better to write: "Can we change 'X' to 'Y' to match the wording of the marketing page?".
[0]: https://marketplace.visualstudio.com/items?itemName=vivaxy.v...