<?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>Wed, 09 Jul 2008 07:14:40 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Designing Klingon Warships Using Behaviour Driven Development]]></title>
      <guid>http://www.phpdeveloper.org/news/9608</guid>
      <link>http://www.phpdeveloper.org/news/9608</link>
      <description><![CDATA[<p>
The Zend Developer Zone has <a href="http://devzone.zend.com/article/3082-Designing-Klingon-Warships-Using-Behaviour-Driven-Development">another new tutorial</a> from <i>Padraic Brady</i> talking about testing your applications (i.e. unit tests). In this new article, he expands on his <a href="http://devzone.zend.com/article/2772-An-Introduction-to-the-Art-of-Unit-Testing-in-PHP">previous one</a> and dives a bit deeper into the behaviour-driven development process.
</p>
<blockquote>
In this article, I introduce a TDD related practice called Behaviour-Driven Development which has been gathering attention for over a year and gaining converts (like me!).
</blockquote>
<p>
He <a href="http://devzone.zend.com/article/3082-Designing-Klingon-Warships-Using-Behaviour-Driven-Development">briefly covers</a> what BDD is and how it can be used to solidify code against issues that might come up down the road (and how it compares to test-driven development). Some sample code/tests are included to give you a better idea of how it all fits together - a set of scenarios for any given "story". True to the title, <i>Padraic</i> writes his tests around the construction of a Klingon Bird of Prey ship. 
</p>]]></description>
      <pubDate>Mon, 11 Feb 2008 15:34:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[O'Reilly: Designing a database-driven PHP App? Don't Forget the Data!!]]></title>
      <guid>http://www.phpdeveloper.org/news/5274</guid>
      <link>http://www.phpdeveloper.org/news/5274</link>
      <description><![CDATA[<p>
On the O'Reilly Network's PHP blog today, there's <a href="http://www.oreillynet.com/onlamp/blog/2006/04/designing_a_databasedriven_php.html?CMP=OTC-6YE827253101&ATT=Designing+a+database-driven+PHP+App+Don+t+Forget+the+Data">a new post</a> <i>bk jones</i> that looks at the other side of application design, from the data's perspective.
</p>
<quote>
<i>
<p>
If you have a sourceforge account, and are on your way to becoming the best thing to happen to the web since Yahoo or Google, then I beg of you to put a call out for people who understand database design fundamentals.
</p>
<p>
Here's the story: If you're a PHP developer, I don't really want you to learn how to design a database. No, really. I don't. I want you to write PHP. There are few people who do both things extremely well, because both take a good bit of time. If you're a PHP developer, I want you to write code that'll make my head spin. However, the path to greatness is to be conscious of your own ignorance - so just acknowledge that you've never done or studied database design, and go find someone who has!
</p>
</i>
</quote>
<p>
He <a href="http://www.oreillynet.com/onlamp/blog/2006/04/designing_a_databasedriven_php.html?CMP=OTC-6YE827253101&ATT=Designing+a+database-driven+PHP+App+Don+t+Forget+the+Data">mentions</a> three misconceptions to consider and avoid when developing a PHP application:
<ul>
<li>The interface determines database design
<li>"I only need a small, simple database"
<li>"More tables makes for harder coding"
</ul>
</p>]]></description>
      <pubDate>Mon, 01 May 2006 07:18:06 -0500</pubDate>
    </item>
  </channel>
</rss>
