<?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 07:57:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Keith Casey's Blog: Useful Naming Conventions]]></title>
      <guid>http://www.phpdeveloper.org/news/11538</guid>
      <link>http://www.phpdeveloper.org/news/11538</link>
      <description><![CDATA[<p>
In a <a href="http://CaseySoftware.com/blog/useful-naming-conventions">new post</a> to his blog <i>Keith Casey</i> shares a few tips on naming conventions that can help increase readability in your code and make maintenance simpler in the future.
</p>
<blockquote>
In my regular web wanderings recently, I found a great post entitled "<a href="http://www.gameproducer.net/2008/11/11/the-7-worst-verbs-programmers-use-in-function-calls/">The 7 Worst Verbs Programmers Use In Function Calls</a>" and couldn't help but be reminded of a system that I worked on a few years ago.  The core function of the system was named - no kidding - "doStuff".  Everything in the application led towards that, used it, and then did other things as a result.
</blockquote>
<p>
He suggests a structure he uses - "verbAjectiveNounStructure". Starting with an action, moving to a description of the action, to the target of the action and finally an optional structure - how the returned data is formatted.
</p>]]></description>
      <pubDate>Tue, 09 Dec 2008 15:31:15 -0600</pubDate>
    </item>
  </channel>
</rss>
