<?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>Sat, 18 May 2013 04:10:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SitePoint PHP Blog: Evaluating PHP Applications]]></title>
      <guid>http://www.phpdeveloper.org/news/5043</guid>
      <link>http://www.phpdeveloper.org/news/5043</link>
      <description><![CDATA[People like simple solutions - they like to go out, find a piece of software that does what they want, and push it out into the wild of the internet on their site. More often than not, unfortunately, they don't take the proper time to really look over the application. They breeze right past that state and install it without a care in the world. Too bad this can lead to bigger issues down the line.
<p>
In order to help ease this problem, <i>Harry Fuecks</i> has <a href="http://www.sitepoint.com/blogs/2006/03/24/evaluating-php-applications/">a post</a> on the SitePoint blog with a few tips on how to evaluate your PHP applications before you even install them.
<p>
<quote>
<i>
Now not everyone is a programmer or a system administrator-"normal human beings" rank these highly because they relate directly to the two most pressing problems they're facing: they want a site which is visually attractive and, with limited technical expertise, installation can be a significant hurdle to overcome.
<p>
But when it comes to security or maintenance, those requirements rank pretty low down. So here's some different things to think about, following on from <a href="http://zh.phpug.ch/_media/meetings/phpsecprimer.pdf?id=meetings%3A20060314&cache=cache">this talk</a> (PDF) on page 19, which I'd argue rank much higher when evaluating a project you plan to use (further suggestions appreciated).
</i>
</quote>
<p>
The points he mentions include:
<ul>
<li>What's the security record like?
<li>What's the code like?
<li>Who's using it?
</ul>
For <a href="http://www.sitepoint.com/blogs/2006/03/24/evaluating-php-applications/">each</a>, he describes why the step is important and how you can work through it - even if you're not that technical. Personally, I'd start with the last one on his list - "Who's got an opinion?" - and work my way from there. If there's one thing it's good for, the internet is definitely a great place to get opinions. So, Google the best you can before even considering a piece of software - it might yield some interesting results.]]></description>
      <pubDate>Fri, 24 Mar 2006 07:20:12 -0600</pubDate>
    </item>
  </channel>
</rss>
