<?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, 25 May 2013 10:08:57 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Anna Filina: Like Athletes, Developers Need Practice Before Performing]]></title>
      <guid>http://www.phpdeveloper.org/news/19353</guid>
      <link>http://www.phpdeveloper.org/news/19353</link>
      <description><![CDATA[<p>
<i>Anna Filina</i> has a new post to her site today suggesting that <a href="http://annafilina.com/blog/practice-vs-performance/">developers are like athletes</a>, they need to practice before they can be good at what they do.
</p>
<blockquote>
Think of  a developer as an athlete. He or she is aiming for a medal in a competition. A figure skater can't just perform a triple axel in the Olympics after seeing it done on television. This requires a lot of practice, so that when the time comes, the performance is flawless. Of course, programming doesn't have to be flawless. One must remain pragmatic, yet it still requires practice before a concept can be safely implemented without breaking the project or missing deadlines. Who will pay for that practice?
</blockquote>
<p>
She relates the development manager to the coach of a sports team, being the one that guides the developers into being all they can be and trying out new ideas in the process. She also recommends making use of idle time between projects to prototype, do R&D and learn in general. 
</p>
<blockquote>
Developers need a sandbox. If you don't give it to them, you can end up with one of the following issues. Your entire project could become a sandbox, making it unstable. [...] If you want your developers to get better, allow time for practice, not just learning. It's necessary, easy to do when planned and provides countless benefits to your company. Let me know how that advice worked out for you.
</blockquote>]]></description>
      <pubDate>Fri, 22 Mar 2013 13:51:55 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Community News: From the SunshinePHP Blog: SunshinePHP is a PHP community event]]></title>
      <guid>http://www.phpdeveloper.org/news/19015</guid>
      <link>http://www.phpdeveloper.org/news/19015</link>
      <description><![CDATA[<p>
Over on the blog for the Sunshine PHP conference (happening next month, February 8th and 9th in Miami, Florida) they've <a href="http://sunshinephp.com/sunshinephp-is-a-php-community-event/">posted a clarification</a> about the intentions of the event and a reminder that it's a "by developers, for developers" event.
</p>
<blockquote>
Recently we overheard SunshinePHP being grouped together with commercial "for profit" events and conferences, which prompted us to write this blog post to clear things up.  The SunshinePHP Developer Conference is NOT a profit driven event, and is actually a community led event by developers, for developers.  Early on we tried to make this more public, but it appears the message was lost with everything the conference contains. (we've made it too good)
</blockquote>
<p>
They note that any profits made from the event will be going back into future events (as put on by the user group) and the PHP community. This kind of thing is similar to some of the other PHP user group-organized conference that have popped up over the last year - good to see the trend continue.
</p>
<p>
If you're interested in the conference itself, you can find out more on <a href="http://sunshinephp.com/">the main event site</a> or just go ahead and <a href="http://sunshinephp.com/register/">register for the event</a>. You can still pick up your tickets until February 1st for about $220 USD (General admission) or $160 USD (Student). 
</p>]]></description>
      <pubDate>Wed, 09 Jan 2013 16:25:30 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPMaster.com: The 8 Fallacies of Distributed Computing for PHP Developers]]></title>
      <guid>http://www.phpdeveloper.org/news/18111</guid>
      <link>http://www.phpdeveloper.org/news/18111</link>
      <description><![CDATA[<p>
If you're a PHP developer and are working on distributed applications (or might be in the future), you should probably read through <a href="http://phpmaster.com/8-fallacies-of-distributed-computing-for-php-developers/">this new article</a> on PHPMaster.com with 8 common fallacies about these applications and their needs.
</p>
<blockquote>
These fallacies directly relate to us as PHP developers since we build distributed applications each and every day. We build mashups, applications that interact with SOAP and REST services, authenticate users via Facebook, Google, or Twitter APIs, retrieve information from remote databases and caching services, etc. Make no mistake, we're building distributed computer applications. Given that we are building distributed applications, it's important that we understand the eight fallacies and how they affect us.
</blockquote>
<p>Among the list of their fallacies are things like:</p>
<ul>
<li>The Network is Reliable
<li>Bandwidth is Infinite
<li>The Network is Secure
<li>There is One Administrator
</ul>
<p>
Check out <a href="http://phpmaster.com/8-fallacies-of-distributed-computing-for-php-developers/">the full article</a> for the rest of them and summaries of each.
</p>]]></description>
      <pubDate>Tue, 19 Jun 2012 09:19:05 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Nikita Popov's Blog: Understanding PHP's internal array implementation (Part 4)]]></title>
      <guid>http://www.phpdeveloper.org/news/17749</guid>
      <link>http://www.phpdeveloper.org/news/17749</link>
      <description><![CDATA[<p>
<i>Nikita Popov</i> has posted the <a href="http://nikic.github.com/2012/03/28/Understanding-PHPs-internal-array-implementation">fourth part</a> of the "PHP's Source Code for PHP Developers" series he and <i>Anthony Ferrara</i> have been posting. In this latest article in the series, <i>Nikita</i> looks specifically at PHP's array implementation and how it's handed "behind the scenes".
</p>
<blockquote>
Welcome back to the fourth part of the "PHP's Source Code for PHP Developers" series, in which we'll cover how PHP arrays are internally represented and used throughout the code base.
</blockquote>
<p>
He starts with an obvious foundation: "everything's a hash table" (even properties, classes and yes, arrays). He describes what a hash table is and talks about two of the most commonly used versions of it in the PHP source - HashTable and Bucket. He gets into their usage a bit and compares this to the corresponding PHP code that uses a standard array.
</p>]]></description>
      <pubDate>Thu, 29 Mar 2012 09:16:02 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Nikita Popov's Blog: Understanding PHP's internal function definitions (Part 2)]]></title>
      <guid>http://www.phpdeveloper.org/news/17688</guid>
      <link>http://www.phpdeveloper.org/news/17688</link>
      <description><![CDATA[<p>
Following <a href="http://blog.ircmaxell.com/2012/03/phps-source-code-for-php-developers.html">this recent post</a> from <i>Anthony Ferraara</i> about the source code of the PHP language itself, <i>Nikita Popov</i> is working with him and has produced <a href="http://nikic.github.com/2012/03/16/Understanding-PHPs-internal-function-definitions">the second part</a> of the series, a look at finding the internal function definitions for the PHP functions you use every day.
</p>
<blockquote>
In the <a href="http://blog.ircmaxell.com/2012/03/phps-source-code-for-php-developers.html">previous part</a> ircmaxell explained where you can find the PHP source code and how it is basically structured and also gave a small introduction to C (as that's the language PHP is written in). If you missed that post, you probably should read it before starting with this one. What we'll cover in this article is locating the definitions of internal functions in the PHP codebase, as well as understanding them.
</blockquote>
<p>
He starts with a basic example - a string function, <a href="http://php.net/strpos">strpos</a>. He shows a handy searching trick to help find the actual function definition and which matches should be given priority. He lays out a typical skeleton of a PHP function definition and gets into some detail as to what this particular function does (in C). He briefly mentions the Zend Engine functions and a look ahead to finding classes and methods.
</p>]]></description>
      <pubDate>Mon, 19 Mar 2012 08:17:48 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DZone.com: DevOps for Devs in 3 Steps (Presentation)]]></title>
      <guid>http://www.phpdeveloper.org/news/17013</guid>
      <link>http://www.phpdeveloper.org/news/17013</link>
      <description><![CDATA[<p>
In the "DevOps" section of DZone.com today <i>Mitchell Pronschinske</i> has <a href="http://agile.dzone.com/articles/devops-devs-3-steps">posted the slides</a> for a presentation he gave at the WebTech 2011 conference titled "DevOps for Developers". It gives a good perspective for those used to the coding side of things on what's out there for the server an beyond.
</p>
<blockquote>
A presentation entitled "DevOps for Developers" was given at the WebTech 2011 conference and now the slides are up online for all to see.  I'll summarize the show and let you know where the better slides are so you don't have to flip through the whole thing.  It starts out on an introductory level, but then it gets into some tools and techniques that are talked about less often.
</blockquote>
<p>
Technologies mentioned in the presentation include more familiar development tools like PHP, Apache, HipApache, Gearman, NoSQL and Memcached. There's also some examples of more "devops" things like Vagrant, Puppet and WetWare.
</p>]]></description>
      <pubDate>Wed, 19 Oct 2011 10:57:25 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPClasses.org: Lately in PHP Episode 16 - APC in PHP, MODX CMS, Top Developers]]></title>
      <guid>http://www.phpdeveloper.org/news/16932</guid>
      <link>http://www.phpdeveloper.org/news/16932</link>
      <description><![CDATA[PHPClasses.org has posted their latest episode of their "Lately In PHP" podcast today - <A href="http://www.phpclasses.org/blog/post/160-PHP-540-Will-not-Include-APC-Is-MODX-CMS-better-than-Wordpress-Top-PHP-Developers-in-Every-Country--Lately-in-PHP-Episode-16.html">PHP 5.4.0 Will not Include APC, Is MODX CMS better than Wordpress? Top PHP Developers in Every Country</a>.
</p>
<blockquote>
PHP 5.4 beta 1 was released but APC is not going to be included at least in PHP 5.4.0. Manuel Lemos and Ernani Joppert discuss this and other happenings in the PHP world, like the adoption of more robust Continuous Integration methods to prevent shipping buggy PHP versions like what happened with PHP 5.3.7.
</blockquote>
<p>
The podcast also features an interview with <i>Bob Ray</i>, an author and contributor to the <a href="http://www.modx.com/">MODX CMS platform</a> project. You can listen to this latest episode either through <a href="http://www.phpclasses.org/blog/post/160-PHP-540-Will-not-Include-APC-Is-MODX-CMS-better-than-Wordpress-Top-PHP-Developers-in-Every-Country--Lately-in-PHP-Episode-16.html">the in-page player</a>, by <a href="http://www.phpclasses.org/blog/post/160/file/88/name/Lately-In-PHP-16.mp3">downloading it directly</a> or by <a href="http://www.phpclasses.org/blog/category/podcast/post/latest.rss">subscribing to their feed</a> and getting this and past shows automatically.
</p>
]]></description>
      <pubDate>Fri, 30 Sep 2011 09:11:53 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Cal Evans' Blog: How do I find good PHP developers?]]></title>
      <guid>http://www.phpdeveloper.org/news/15126</guid>
      <link>http://www.phpdeveloper.org/news/15126</link>
      <description><![CDATA[<p>
If you or your company is looking to hire on PHP developers but are having trouble finding good, qualified people, you should check out <a href="http://blog.calevans.com/2010/09/11/how-do-i-find-good-php-developers/">some of the advice</a> that <i>Cal Evans</a> has posted to his blog to help you out.
</p>
<blockquote>
Twice this week I got asked a similar question, "How do I find good PHP developers to hire?" The first one was a recruiter who had originally tried to hire me because she "read my resume". [...] The second one, however, was a just someone trying to find PHP developers for his team. Since he wrote me a nice email asking advice, I decided to reply in kind. Three pages and one thousand words later, he had my answer.
</blockquote>
<p>
His answer included seven different points companies/recruiters could possibly follow to help them get the right people on board:
</p>
<ul>
<li>posting jobs on <a href="http://phpdeveloper.org/">phpdeveloper.org</a> (yes, shameless self-promotion)
<li>PHP User Groups
<li>Getting involved in the community 
<li>Considering telecommuters
<li>Attending conferences
<li>Getting your developers to write about your company/work environment
<li>Do things that make your developers want to sing your praises
</ul>]]></description>
      <pubDate>Tue, 14 Sep 2010 12:22:14 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Hartjes' Blog: Twitter Asks: Continuous Integration Landscape for PHP Developers]]></title>
      <guid>http://www.phpdeveloper.org/news/15094</guid>
      <link>http://www.phpdeveloper.org/news/15094</link>
      <description><![CDATA[<p>
After asking for topics to blog about on Twitter, <i>Chris Hartjes</i> has posted the first response to the suggestions - a look at <a href="http://www.littlehart.net/atthekeyboard/2010/09/07/twitter-asks-continuous-integration-landscape-for-php-developers/">continuous integration</a> (CI) in PHP environments.
</p>
<blockquote>
For those not familiar with the concept of Continuous Integration, I can sum it up with one very glib phrase: it lets you break your code before you buy it. [...] If I were to design a Continuous Integration (hereafter referred to as CI) system, what would it look like?
</blockquote>
<p>
His requirements include version control integration, easy unit test execution, a web interface and be able to automate it all at a moment's notice. He talks about the importance of unit testing in CI and the tools that are available for the job like <a href="http://phpundercontrol.org/">phpUnderControl</a>, <a href="http://code.google.com/p/xinc/">Xinc</a> and <a href="http://hudson-ci.org/">Hudson</a>. He also looks at the build process, from check-in through a successful build result and how he handles bugs when they do pop up.
</p>]]></description>
      <pubDate>Wed, 08 Sep 2010 10:42:42 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[WebHostingHero Blog: A Look at the Original PHP Developers]]></title>
      <guid>http://www.phpdeveloper.org/news/14863</guid>
      <link>http://www.phpdeveloper.org/news/14863</link>
      <description><![CDATA[<p>
On the WebHostingHero blog today there's <a href="http://www.webhostinghero.ca/the-original-php-developers.html">a new post</a> going back to the roots of the PHP language and some of the original contributors like <i>Rasmus Lerdorf</i>, <i>Zeev Suraski</i> and <i>Andi Gutmans</i>.
</p>
<blockquote>
When PHP began in 1995, it represented a fork on common object oriented programming languages. Designed to help provide scripting for the web, the language took on a life of its own as it became one of the primary web development standards. Today, PHP is used by millions worldwide and powers a majority of sites.
</blockquote>
<p>
They talk about how some of the original developers are active in helping to better the languages (directly and indirectly) and how the advocacy of the community has helped it grow even stronger over the years. There's also mini-spotlights on each of the three mentioned above.
</p>]]></description>
      <pubDate>Wed, 28 Jul 2010 09:44:23 -0500</pubDate>
    </item>
  </channel>
</rss>
