<?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>Sat, 25 May 2013 04:51:29 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Practical Code Refactoring, Part 3 - Extensibility]]></title>
      <guid>http://www.phpdeveloper.org/news/18655</guid>
      <link>http://www.phpdeveloper.org/news/18655</link>
      <description><![CDATA[<p>
PHPMaster.com has posted the third part in their "Practical Code Refactoring" series - this time with a <a href="http://phpmaster.com/practical-code-refactoring-3/">focus on Extensibility</a>. (<a href="http://phpmaster.com/practical-refactoring-1/">Part 1</a>, <a href="http://phpmaster.com/practical-code-refactoring-2/">Part 2</a>).
</p>
<blockquote>
Extensible code is a piece of code which follows re-usable, logical, well-known patterns, be it standard design patterns, or normal logical flow. Modular code tends to be highly extensible and monolithic code tends to be non-extensible, but monolithic code might be more efficient, so to solve this conundrum some practices allow developing in a modular way and deploying in a monolithic way so we can get the best of both worlds. The major aspects which we are to discuss with regard to extensible code are: logical extensibility (normal logical flow and design patterns), modular design, and decoupling and encapsulation.
</blockquote>
<p>
He goes through each of the sections - logical extensibility, modular design and decoupling/encapsulation - and for each provides some questions to ask to help you whip your code into shape.
</p>]]></description>
      <pubDate>Thu, 25 Oct 2012 09:22:05 -0500</pubDate>
    </item>
  </channel>
</rss>
