<?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>Sun, 19 May 2013 04:56:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Quoderat's Blog: Three simple tips for LAMP web site developers]]></title>
      <guid>http://www.phpdeveloper.org/news/8316</guid>
      <link>http://www.phpdeveloper.org/news/8316</link>
      <description><![CDATA[<p>
On Quoderat's blog today, there's a <a href="http://www.megginson.com/blogs/quoderat/2007/07/21/three-simple-tips-for-lamp-web-site-developers/">post with a few simple tips</a> (three of them) to help out LAMP web site developers:
</p>
<blockquote>
You've learned to write some basic HTML, CSS, PHP/Python/Perl and SQL, found a hosting service, and are ready to create your first LAMP web application. You've already read a bit about security (you know always to escape user-supplied parameters, etc.). Here are a three very simple tips that will help you along right at the start, without getting caught up in religious wars about frameworks, MVC, REST, abstraction, object orientation, etc.
</blockquote>
<p>
<a href="http://www.megginson.com/blogs/quoderat/2007/07/21/three-simple-tips-for-lamp-web-site-developers/">The tips</a> (summed up) are:
</p>
<ul>
<li>Keep all the database code together
<li>Make an extra database for junk.
<li>Make GET harmless.
</ul>
<p>
...with the requisite explanations for each.
</p>]]></description>
      <pubDate>Tue, 24 Jul 2007 09:32:00 -0500</pubDate>
    </item>
  </channel>
</rss>
