<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Halfbakery on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/halfbakery/</link>
    <description>Recent content in Halfbakery on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 Dec 2017 00:40:32 -0600</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/halfbakery/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Maybe Comments SHOULD Explain &#39;What&#39;</title>
      <link>https://www.hillelwayne.com/post/what-comments/</link>
      <pubDate>Tue, 05 Dec 2017 00:40:32 -0600</pubDate>
      
      <guid>https://www.hillelwayne.com/post/what-comments/</guid>
      <description>People say &amp;ldquo;Comments should explain why, not what.&amp;rdquo; I feel like starting a flame war today so I&amp;rsquo;m going to argue that comments should explain &amp;lsquo;what&amp;rsquo; too. Please don&amp;rsquo;t use this as justification to write bad code, okay? Okay.
First of all, why shouldn&amp;rsquo;t comments explain &amp;lsquo;what&amp;rsquo;? If you need comments to explain what&amp;rsquo;s going on, it suggests your code is unclear. If I write
//weight, radius, price w = 10, r = 9, p = 1  That&amp;rsquo;s not as clear as saying</description>
    </item>
    
  </channel>
</rss>