Reflections on 10k Hours of Programming
Author here, thanks for posting.<p>Here&#x27;s some more color on the reflection on comments, straight from the Linux Kernel documentation that capture my intention much better:<p><i>&quot;Comments are good, but there is also a danger of over-commenting. NEVER try to explain HOW your code works in a comment: it’s much better to write the code so that the working is obvious, and it’s a waste of time to explain badly written code.<p>Generally, you want your comments to tell WHAT your code does, not HOW. Also, try to avoid putting comments inside a function body: if the function is so complex that you need to separately comment parts of it, you should probably go back to chapter 6 for a while. You can make small comments to note or warn about something particularly clever (or ugly), but try to avoid excess. Instead, put the comments at the head of the function, telling people what it does, and possibly WHY it does it.&quot;</i>[0]<p>[0] <a href="https:&#x2F;&#x2F;www.kernel.org&#x2F;doc&#x2F;html&#x2F;v4.10&#x2F;process&#x2F;coding-style.html#commenting" rel="nofollow">https:&#x2F;&#x2F;www.kernel.org&#x2F;doc&#x2F;html&#x2F;v4.10&#x2F;process&#x2F;coding-style.h...</a>