<?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 10:56:24 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[php|architect Blog: Opinion: Arrogance is Limiting Framework Adoption]]></title>
      <guid>http://www.phpdeveloper.org/news/12692</guid>
      <link>http://www.phpdeveloper.org/news/12692</link>
      <description><![CDATA[<p>
On the php|architect blog there's a <a href="http://phparch.com/c/news/view/10">new post</a> from <i>Cal Evans</i> (of Ibuildings) with what he thinks is one of the largest reasons that frameworks aren't as well-adopted as they should be - arrogance.
</p>
<blockquote>
Developers are notoriously self-confident in their ability to write code that is better, faster, cleaner and better-smelling than everybody else's. In today's environment, however, the focus is on producing immediately useful code'"and, given the richness of today's frameworks, those who eschew them in favour of home-grown solutions are forever running the risk of reinventing the wheel for no good reason. We have enough wheels'"start building some cars. 
</blockquote>
<p>
He suggests that, with all of the "reinventing the wheel" that's been going on and overpowering frameworks that are out there, that developers need to take a step back and find a framework that fits for them. Coding from scratch (usually) isn't a good option - there's almost always a framework or application based on one out there that'll fit with just what you need.
</p>
<blockquote>
Pick a framework that has a thriving community and then spend the time to learn it. Quit re-inventing the wheel, start using the wheel to solve your client's problems. Get out there and build them a car.
</blockquote>]]></description>
      <pubDate>Tue, 16 Jun 2009 08:49:04 -0500</pubDate>
    </item>
  </channel>
</rss>
