<?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>Thu, 23 May 2013 08:06:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Rob Allen's Blog: What problem does dependency injection solve?]]></title>
      <guid>http://www.phpdeveloper.org/news/17560</guid>
      <link>http://www.phpdeveloper.org/news/17560</link>
      <description><![CDATA[<p>
In his latest post <i>Rob Allen</i> seeks to answer the question "<a href="http://akrabat.com/zend-framework-2/what-problem-does-dependency-injection-solve/">what problem does dependency injection solve?":
</p>
<blockquote>
Zend Framework 2 comes with a <a href="http://packages.zendframework.com/docs/latest/manual/en/zend.di.html">dependency injection container</a> (DIC), as does Symfony 2 and Aura, along with many other PHP frameworks that target PHP 5.3 or hight nowadays. This article attempts to explore the problem that a DIC tries to solve.
</blockquote>
<p>
He gives an example (somewhat based on the same structure of his <a href="http://akrabat.com/zend-framework-tutorial">Zend Framework tutorial</a>) showing how you could use DI to inject the Artist object into the Album object. This allows for more flexibility if more Artist types are added (extending the main Artist, of course). His second example shows how to use a DIC to hold album information.
</p>
]]></description>
      <pubDate>Mon, 20 Feb 2012 09:37:15 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Fabien Potencier's Blog: Developers should be Artists]]></title>
      <guid>http://www.phpdeveloper.org/news/13113</guid>
      <link>http://www.phpdeveloper.org/news/13113</link>
      <description><![CDATA[<p>
<i>Fabien Potencier</i> <a href="http://fabien.potencier.org/article/32/developers-should-be-artists">has a suggestion</a> for developers out there - don't just look at what you write as something functional that just does a job, be an artist!
</p>
<blockquote>
Hacking is an art, and hackers should act as artists. Hackers and painters have a lot in common but I won't talk about the analogy too much as Paul Graham wrote an excellent <a href="http://www.paulgraham.com/hp.html">essay</a> and a whole <a href="http://www.paulgraham.com/hackpaint.html">book</a> on this topic. I recommend you to read both of them if you are a hacker or a developer.
</blockquote>
<p>
He points out that "beautiful code" is a good thing - unfortunately developers for companies may not have the luxury of writing it. He does suggest hacking on your own time, though. Not only is it good for you, getting out those ideas into working code, but it can also positively effect the applications you develop at your work.
</p>
]]></description>
      <pubDate>Wed, 26 Aug 2009 10:17:14 -0500</pubDate>
    </item>
  </channel>
</rss>
