<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.oehive.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>schlatter&#039;s blog</title>
 <link>http://www.oehive.org/blog/455</link>
 <description></description>
 <language>oehive</language>
<item>
 <title>Code Standards - developing a manual</title>
 <link>http://www.oehive.org/node/733</link>
 <description>&lt;p&gt;I am working on a manual of code standards for my division, and would appreciate input about this.  I&#039;ve incorporated (or adapted) many of the entries from the prolint lists of bugs, style improvement, performance enhancements, etc.   Of course this will be a combination of helpful advice, common sense, ways to make the code more readable and re-usable, and ways to prevent problems down the line.&lt;/p&gt;
&lt;p&gt;I will appreciate any suggestions or ideas that are sent in.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/devtools&quot; class=&quot;og_links&quot;&gt;Development Tools Group&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description>
 <comments>http://www.oehive.org/node/733#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/271">performance</category>
 <category domain="http://www.oehive.org/taxonomy/term/270">Standards</category>
 <category domain="http://www.oehive.org/taxonomy/term/272">tools</category>
 <category domain="http://www.oehive.org/taxonomy/term/133">Coding Standards and Best Practice</category>
 <category domain="http://www.oehive.org/taxonomy/term/214">Development Support Tools</category>
 <group domain="http://www.oehive.org/devtools">Development Tools Group</group>
 <pubDate>Mon, 26 Feb 2007 16:46:03 +0000</pubDate>
 <dc:creator>schlatter</dc:creator>
 <guid isPermaLink="false">733 at http://www.oehive.org</guid>
</item>
</channel>
</rss>
