<?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>Mon, 20 May 2013 02:00:50 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Samuel Folkes' Blog: 17 PHP Practices That Should Be Banished Forever]]></title>
      <guid>http://www.phpdeveloper.org/news/13001</guid>
      <link>http://www.phpdeveloper.org/news/13001</link>
      <description><![CDATA[<p>
<i>Samuel Folkes</i> has <a href="http://www.samuelfolkes.com/2009/08/17-php-practices-that-should-be-banished-forever/">posted a few practices</a> (seventeen, to be exact) that PHP developers should "banish forever" from their development habits.
</p>
<blockquote>
The following is a list of 17 PHP programming practices that in my opinion should be banished into oblivion. Forever and ever. Amen. Please note that this list is in no particular order.
</blockquote>
<p>Some of the practices include:</p>
<ul>
<li>Relying on Magic Quotes
<li>Mixing HTML, PHP, SQL, JS, CSS, Etc, Etc
<li>Not Documenting Code
<li>Using Regex Functions for Basic String Manipulation.
<li>Unquoted Array Keys
<li>Using Uninitialized Variables
</ul>
<p>
There's lots more where those came from so check out the <a href="http://www.samuelfolkes.com/2009/08/17-php-practices-that-should-be-banished-forever/">rest of the list here</a>.
</p>]]></description>
      <pubDate>Wed, 05 Aug 2009 13:37:17 -0500</pubDate>
    </item>
  </channel>
</rss>
