<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>hcarvalhoalves</author><text>It seems I disagree w&amp;#x2F; many points.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;gt; - Leave actionable comments
    &amp;gt; suggestion: This is not worded correctly.
    &amp;gt; Can we change this to match the wording of the marketing page?
&lt;/code&gt;&lt;/pre&gt;
If I already know how it should be, I prefer to quote it right away and save work, instead of asking and leaving room for misinterpretation. Asking also seems dishonest if I&amp;#x27;m not truly inviting a discussion. I would still add a rationale so others can correct me though (&amp;quot;Changing this to match the wording on the marketing page&amp;quot;).&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;gt; - Combine similar comments
&lt;/code&gt;&lt;/pre&gt;
Sometimes it&amp;#x27;s better to be repetitive in the name of exactness, because most review tools are line-oriented. Otherwise I have to write a comment &amp;quot;See lines A, B, C, D, E&amp;quot;, and the person asking for the review now has more work to do searching all the instances.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;gt; - Replace “you” with “we”
&lt;/code&gt;&lt;/pre&gt;
Better yet, I replace all pronouns w&amp;#x2F; &amp;quot;this&amp;quot;. Criticise the work, don&amp;#x27;t make it personal if it&amp;#x27;s not necessary. &amp;quot;We&amp;quot; feels forced team-building, and dishonest if I&amp;#x27;m not actually going to put in work.&lt;p&gt;It seems these practices are created because people are using reviews as some form of conversation, and then everybody is stepping on egg shells. I believe if the entire team agrees to see it as just annotations (it&amp;#x27;s not a performance evaluation, leave your ego at the door, etc) these problems are avoided.&lt;p&gt;(I can see &amp;quot;why&amp;quot; you need these guidelines though, I guess it depends on what kind of work culture you have, company size, and so on.)</text><parent_chain></parent_chain></comment><story><title>Conventional Comments</title><url>https://conventionalcomments.org/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jchw</author><text>I agree with the vast majority of this, but I have a bad reaction to “praise” and the idea that you should try to have one per review. I hate praise that feels forced, and it seems like this kind of practice would make it seem quite forced.&lt;p&gt;I feel you could just say something like “good idea” and it would be fine without the prefix. Especially if your review tool of choice has a concept of actionable vs non-actionable comments, like Gerrit and resolved&amp;#x2F;unresolved comments.</text><parent_chain></parent_chain></comment><story><title>Conventional Comments</title><url>https://conventionalcomments.org/</url></story>