<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Surfsoft Consulting Blog &#187; Best Practice</title>
	<atom:link href="http://blog.surfsoftconsulting.com/tag/best-practice/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.surfsoftconsulting.com</link>
	<description>Java, enterprise applications, software engineering and general technical geekery</description>
	<lastBuildDate>Sat, 04 Feb 2012 12:04:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Build Your Software on Firm Foundations&#8230;</title>
		<link>http://blog.surfsoftconsulting.com/2009/03/build-your-software-on-firm-foundations/</link>
		<comments>http://blog.surfsoftconsulting.com/2009/03/build-your-software-on-firm-foundations/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 22:22:00 +0000</pubDate>
		<dc:creator>Phil</dc:creator>
				<category><![CDATA[Software Architecture]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Software Architecture Document]]></category>

		<guid isPermaLink="false">http://localhost/~phil/?p=21</guid>
		<description><![CDATA[What makes for a successful software development project? I was mulling over a number of projects I had been involved with in the past, some very successful, some not so, and thinking about the key differences between the two. There are any number of aspects that can be considered &#8211; the quality of project management, &#8230; </p><p><a class="more-link block-button" href="http://blog.surfsoftconsulting.com/2009/03/build-your-software-on-firm-foundations/">Continue reading &#187;</a>]]></description>
		<wfw:commentRss>http://blog.surfsoftconsulting.com/2009/03/build-your-software-on-firm-foundations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top 25 Most Dangerous Programming Errors</title>
		<link>http://blog.surfsoftconsulting.com/2009/01/top-25-most-dangerous-programming-errors/</link>
		<comments>http://blog.surfsoftconsulting.com/2009/01/top-25-most-dangerous-programming-errors/#comments</comments>
		<pubDate>Thu, 15 Jan 2009 22:14:40 +0000</pubDate>
		<dc:creator>Phil</dc:creator>
				<category><![CDATA[Engineering Process]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Standards]]></category>

		<guid isPermaLink="false">http://localhost/~phil/?p=20</guid>
		<description><![CDATA[The SANS Institute has published a list of the top 25 most dangerous programming errors and reading through the list was pretty much like meeting a bunch of old friends. Such lists may seem self evident to some but that doesn&#8217;t stop development teams falling into the same traps today that were being fallen into &#8230; </p><p><a class="more-link block-button" href="http://blog.surfsoftconsulting.com/2009/01/top-25-most-dangerous-programming-errors/">Continue reading &#187;</a>]]></description>
		<wfw:commentRss>http://blog.surfsoftconsulting.com/2009/01/top-25-most-dangerous-programming-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Method Contracts! Method Contracts! Method Contracts!</title>
		<link>http://blog.surfsoftconsulting.com/2008/07/method-contracts-method-contracts-method-contracts/</link>
		<comments>http://blog.surfsoftconsulting.com/2008/07/method-contracts-method-contracts-method-contracts/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 20:23:00 +0000</pubDate>
		<dc:creator>Phil</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Engineering Process]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://localhost/~phil/?p=14</guid>
		<description><![CDATA[I recently spent a few days back-filling test code to help a team meet one of its its quality objectives &#8211; namely unit test coverage &#8211; and the scany level of documentation within the code re-enforced my views on properly documenting the contract of a method. The methods I wrote tests for had the minimum &#8230; </p><p><a class="more-link block-button" href="http://blog.surfsoftconsulting.com/2008/07/method-contracts-method-contracts-method-contracts/">Continue reading &#187;</a>]]></description>
		<wfw:commentRss>http://blog.surfsoftconsulting.com/2008/07/method-contracts-method-contracts-method-contracts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing, testing</title>
		<link>http://blog.surfsoftconsulting.com/2008/02/testing-testing/</link>
		<comments>http://blog.surfsoftconsulting.com/2008/02/testing-testing/#comments</comments>
		<pubDate>Wed, 13 Feb 2008 10:23:00 +0000</pubDate>
		<dc:creator>Phil</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Engineering Process]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[OO]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://localhost/~phil/?p=4</guid>
		<description><![CDATA[There&#8217;s a lot to be said for test driven development. Next to documenting the code, testing is the other bane of a developer&#8217;s life that prevents them from moving on and doing other, &#8216;more interesting&#8217; work. All the better then that the approach to writing code should include the writing of test cases. Write some &#8230; </p><p><a class="more-link block-button" href="http://blog.surfsoftconsulting.com/2008/02/testing-testing/">Continue reading &#187;</a>]]></description>
		<wfw:commentRss>http://blog.surfsoftconsulting.com/2008/02/testing-testing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

