<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>classified</author><text>&amp;gt; ... not so good code: if it was, we wouldn’t need a comment...&lt;p&gt;How much longer will this rumor persist that &amp;quot;good code&amp;quot; doesn&amp;#x27;t need commenting? Good comments explain things that aren&amp;#x27;t immediately obvious from the code.</text><parent_chain></parent_chain></comment><story><title>The Shapes of Code</title><url>https://www.fluentcpp.com/2020/01/14/the-shapes-of-code/</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>saltyfamiliar</author><text>I&amp;#x27;m glad I&amp;#x27;m not the only one who pays attention to this. This is completely unsubstantiated and coming from a relatively inexperienced programmer, but it&amp;#x27;s been my experience that better code tends to produce nicer shapes. An obvious example not mentioned in the article arises when code is nested too deeply and too thinly, creating jarring and disproportionate peaks.</text><parent_chain></parent_chain></comment><story><title>The Shapes of Code</title><url>https://www.fluentcpp.com/2020/01/14/the-shapes-of-code/</url></story>