<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 10:34:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHP in Action: More beautiful code]]></title>
      <guid>http://www.phpdeveloper.org/news/11376</guid>
      <link>http://www.phpdeveloper.org/news/11376</link>
      <description><![CDATA[<p>
Continuing on from a previous post, the PHP in Action blog <a href="http://www.reiersol.com/blog/1_php_in_action/archive/169_more_beautiful_code.html">takes another look</a> at their suggestions on "beautiful code" with some responses to the <A href="http://www.reiersol.com/blog/1_php_in_action/archive/168_beautiful_code.html">previous post</a>.
</p>
<blockquote>
I got some interesting comments to my previous post on "beautiful code". Some were pretty strong disagreements. So am I wrong? Did I get carried away? Did my critical faculty go on vacation somewhere nice and sunny? [...] My main point is that it's close to plain English. Not everyone agrees that that's a good thing, but I argue that we're built (genetically wired, in fact) to understand natural languages, not program code.
</blockquote>
<p>
He reasons that code should be easier to understand than just a bunch of random functions and parameters jumbled together. He thinks that it should read more like a human could understand rather than just the machine. With function names like "assertThat" and "hasSelect", it does make it easier to follow.
</p>]]></description>
      <pubDate>Mon, 10 Nov 2008 10:25:34 -0600</pubDate>
    </item>
  </channel>
</rss>
