<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>p3ll0n</author><text>Four rules that should be tattooed on the back of every technical writer’s hands so they can’t accidentally forget it.&lt;p&gt;1. Poor grammar and bad writing are often a sign of poor comprehension.&lt;p&gt;2. Good documentation takes time.&lt;p&gt;3. Deep expertise is not automatically a prerequisite for good documentation.&lt;p&gt;4. Don’t let working cultures that put too great a premium on knowing everything dominate - i.e. being &apos;in the know&apos; should be a tool for helping others up rather than beating them down.</text><parent_chain></parent_chain></comment><story><title>Writing great documentation</title><url>http://jacobian.org/writing/great-documentation/</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>frossie</author><text>I wish I could upvote this ten times.&lt;p&gt;I loved the comment about not making your tutorial so easy that it becomes unrepresentative of the level required to use the technology.</text><parent_chain></parent_chain></comment><story><title>Writing great documentation</title><url>http://jacobian.org/writing/great-documentation/</url></story>