<?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>Tue, 21 May 2013 20:39:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Misko Hevery's Blog: Guide: Writing Testable Code]]></title>
      <guid>http://www.phpdeveloper.org/news/11690</guid>
      <link>http://www.phpdeveloper.org/news/11690</link>
      <description><![CDATA[<p>
In <a href="http://misko.hevery.com/code-reviewers-guide/">this slightly older (Nov 2008) but useful post</a> to <i>Misko</i>'s blog, he takes a look at a few common flaws that you should avoid in writing up your code (in any language really).
</p>
<blockquote>
To keep our code at Google in the best possible shape we provided our software engineers with these constant reminders. Now, we are happy to share them with the world.
</blockquote>
<p>Here's the list of the flaws:</p>
<ul>
<li>Flaw #1: Constructor does Real Work
<li>Flaw #2: Digging into Collaborators
<li>Flaw #3: Brittle Global State & Singletons
<li>Flaw #4: Class Does Too Much
</ul>
<p>
Each includes some warning signs to keep an eye out for to see if you and your code might be straying the wrong way.
</p>]]></description>
      <pubDate>Wed, 07 Jan 2009 10:29:39 -0600</pubDate>
    </item>
  </channel>
</rss>
