<?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, 26 May 2013 04:03:03 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Troy Hunt: 10 lessons for uncultured web developers]]></title>
      <guid>http://www.phpdeveloper.org/news/18460</guid>
      <link>http://www.phpdeveloper.org/news/18460</link>
      <description><![CDATA[<p>
<i>Troy Hunt</i> has posted <a href="http://www.troyhunt.com/2012/09/10-lessons-for-uncultured-web-developers.html">ten reminders for "uncultured web developers"</a> out there to think about when they're developing applications for a world-wide audience.
</p>
<blockquote>
What a lot of this boils down to is culture, or more specifically, lack of cultural awareness. I'm talking about making assumptions based on what a developer may personally hold to be true but in the broader global context is incorrect and often marginalises their audience. In the pursuit of a more globally harmonious online experience, let's take a look at 10 lessons relating to aspects of web development with a cultural bent. Some of this may not be new to you, but all of it is relevant if you want to play nice with people from all cultural walks of life.
</blockquote>
<p>Among the list of his ten tips you'll find things like:</p>
<ul>
<li>Firefox and Chrome command 91% of the market
<li>Almost always, 8/7 comes before 7/8
<li>Country code top level domains give context
<li>Time zones matter (and they're not universally understood)
<li>Don't deprioritise your international audiences
</ul>
<p>
Check out <a href="http://www.troyhunt.com/2012/09/10-lessons-for-uncultured-web-developers.html">the rest of the list</a> in his full post.
</p>]]></description>
      <pubDate>Mon, 10 Sep 2012 11:53:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: PHP Has No Culture of Testing]]></title>
      <guid>http://www.phpdeveloper.org/news/10161</guid>
      <link>http://www.phpdeveloper.org/news/10161</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> has <a href="http://sebastian-bergmann.de/archives/779-PHP-Has-No-Culture-of-Testing.html">pointed out</a> something obvious to anyone that's ever tried to work with unit tests in PHP - there's just not that much support for it. The software is there and waiting to be used, but too many developers just don't take advantage of it.
</p>
<blockquote>
Maybe it took the PHP community a little longer to realize the importance of testing. But now that we know how to build applications that "just work", are fast and scalable, as well as secure, a big topic in the PHP community right now is to implement processes and use techniques that help us assure that the software works correctly throughout the its lifecycle.
</blockquote>
<p>
He points to some <a href="http://www.infoworld.com/article/08/05/05/rails-php_1.html">comments</a> made at a recent panel discussion about PHP and testing, the proliferation of frameworks for the language and the <a href="http://mysqldump.azundris.com/archives/55-phpvikinger.org-Things-that-have-no-name.html">things that have no name</a> that developers use every day to make their code "just work".
</p>]]></description>
      <pubDate>Mon, 12 May 2008 10:28:26 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Professioanl PHP Blog: Building a culture of objects in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/4657</guid>
      <link>http://www.phpdeveloper.org/news/4657</link>
      <description><![CDATA[From the Professionl PHP Blog today, there's <a href="http://www.procata.com/blog/archives/2006/01/13/building-a-culture-of-objects-in-php/">a followup post</a> to his <a href="http://www.procata.com/blog/archives/2005/09/29/why-isnt-php-the-natural-successor-to-java/">Why isn't PHP the natural successor to Java?</a> post previously - a look at some of the items mentioned in the Zend Framework, branching into a discussion of PHP's object capabilities.
<p>
<quote>
<i>
Joshua Eichorn (<a href="http://shiflett.org/archive/171">among others</a>) notices that <a href="http://blog.joshuaeichorn.com/archives/2006/01/09/zactiverecord-cant-work/">active record can't work</a> as shown in the <a href="http://www.procata.com/blog/archives/2005/12/05/zend-framework-webcast/">Zend Framework webcast</a>. The syntax presented during the web cast is not possible in PHP because of inherited static methods are treated. Mike Naberezny notes the problem and suggests that it will end up getting fixed in PHP, the sitepoint thread <a href="http://www.sitepoint.com/forums/showthread.php?t=334377">Trouble in Zend Framework Land?</a>, 33degrees smells vaporware, and <a href="http://elizabethmariesmith.com/2006/01/09/annoying-statics-in-php/">Elizabeth Marie Smith</a> does too.
<p>
I look at this incident as an incredibly good omen. My optimism about Zend's PHP framework is not for the framework itself, but for what it means for OO support in PHP. In my book, the more developers that have commit access to both ZPF and to PHP, the better PHP 6 will be for me. I look at ZPF as an important step in building a culture of objects in the PHP community.
</i>
</quote>
<p>
He <a href="http://www.procata.com/blog/archives/2006/01/13/building-a-culture-of-objects-in-php/">continues</a>, talking more about how object-oriented languages are still popping up right and left, and how PHP, at its core, needs an OO layer built on top to compare. He's not looking to belittle the OOP support in PHP, just to note that there's more work to be done - and the Zend Framework might be what pushed the development of that along...]]></description>
      <pubDate>Fri, 13 Jan 2006 07:02:02 -0600</pubDate>
    </item>
  </channel>
</rss>
