<?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, 19 Jun 2013 04:28:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: PHP Project Management]]></title>
      <guid>http://www.phpdeveloper.org/news/19340</guid>
      <link>http://www.phpdeveloper.org/news/19340</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new post that takes a different approach to PHP development than some of their articles in the past. It comes at it <a href="http://phpmaster.com/php-project-management/">from the project management side</a> of things, talking more about how to run the project and less about the technology it involves.
</p>
<blockquote>
Whether we like it or not, unless we are doing a hobby project just for our own amusement, even the most technical among us are really just project managers who can code. And, as a project manager, we can experience the heartbreak of project failure. [...] So what can you do as a technical project manager to minimize your chances of adding "leader of a failed project" to your resume? The answer is: pretty much what non-technical project leaders do.
</blockquote>
<p>
He touches on a few key points that are important to any technology project, not just PHP ones - managing the expectations of the team and the business, using iterative processes and development and avoiding scope creep. He also drops in a bit about watching out for "weird stuff" that might be new or different to your group and their technology choices.
</p>]]></description>
      <pubDate>Wed, 20 Mar 2013 15:18:41 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Philip Olson's Blog: 20 possible reasons why PHP function names and parameters are weird]]></title>
      <guid>http://www.phpdeveloper.org/news/7925</guid>
      <link>http://www.phpdeveloper.org/news/7925</link>
      <description><![CDATA[<p>
For your consideration today, <i>Philip Olson</i> has worked up <a href="http://blog.roshambo.org/archives/20-possible-reasons-why-PHP-function-names-and-parameters-are-weird.html">a listing</a> of twenty (humorous) possible reasons that the names of the PHP functions are weird.
</p>
<blockquote>
Here are 20 possible reasons why PHP functions lack consistent names and parameters. Learning the definition for every PHP function is truly an amazing feat and I doubt this has been attempted or accomplished by anyone. At least, by any sane human. And references are named references because they are designed to be referenced, right?
</blockquote>
<p>
Items on <a href="http://blog.roshambo.org/archives/20-possible-reasons-why-PHP-function-names-and-parameters-are-weird.html">the list</a> include:
<ul>
<li>PHP likes BC
<li>PHP says all your namespace are belong to us
<li>PHP function naming algorithm still remains a secret and cannot be cracked
<li>PHP isn't designed to win a beauty contest
</ul>
</p>]]></description>
      <pubDate>Tue, 29 May 2007 07:04:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Mike Wallner's Blog: Cookie Handling]]></title>
      <guid>http://www.phpdeveloper.org/news/5413</guid>
      <link>http://www.phpdeveloper.org/news/5413</link>
      <description><![CDATA[<p>
<i>Mike Wallner</i> is sharing a quick note in <a href="http://blog.iworks.at/?/archives/41-Cookie-Handling.html">this new blog post</a> about some "weirdance" he noticed while working with libcurl and cookies.
</p>
<quote>
<i>
I had to implement some changes which are only in CVS for now. Beware that all this does not affect custom cookies set with <a href="http://dev.iworks.at/ext-http/http-functions.html.gz#HttpRequest_setCookies">HttpRequest::setCookies</a>() and <a href="http://dev.iworks.at/ext-http/http-functions.html.gz#HttpRequest_addCookies">HttpRequest::addCookies</a>(). Custom cookies can always be unset by calling HttpRequest::setCookies().
</i>
</quote>
<p>
He's made <a href="http://blog.iworks.at/?/archives/41-Cookie-Handling.html">these adjustments</a> in the CVS for the library, and mentions an implementation of the cookiestore option with these new changes as well.
</p>]]></description>
      <pubDate>Mon, 22 May 2006 06:03:47 -0500</pubDate>
    </item>
  </channel>
</rss>
