<?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>Sun, 19 May 2013 19:04:36 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brandon Savage's Blog: Stop Sacrificing Readability For Efficiency!]]></title>
      <guid>http://www.phpdeveloper.org/news/12226</guid>
      <link>http://www.phpdeveloper.org/news/12226</link>
      <description><![CDATA[<p>
<i>Brandon Savage</i> <a href="http://www.brandonsavage.net/stop-sacrificing-readability-for-efficiency/">has a recommendation</a> fro developers out there - sometimes readability is more important than any micro-efficiency you might gain in your scripts.
</p>
<blockquote>
Much was made last week over the topic of <a href="http://www.alexatnet.com/node/196">micro optimization</a> in PHP. Most of these argued that micro optimization was a bad idea. [...] There's another reason that micro optimization can be a bad choice: it makes code absolutely impossible to read!
</blockquote>
<p>
He points out one example for validating the length of a string in two ways - one using isset to tell which characters in a string are set and the other using the tride and true call to <a href="http://php.net/strlen">strlen</a>. The first, while benchmarked to give you a (very tiny) improvements, is harder to read at first glance than the check to the string length.
</p>]]></description>
      <pubDate>Fri, 27 Mar 2009 12:58:28 -0500</pubDate>
    </item>
  </channel>
</rss>
