<?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>NMP Blog &#187; Best Practices</title>
	<atom:link href="http://nmpconsulting.com/blog/category/programming/best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://nmpconsulting.com/blog</link>
	<description>Solutions to your technology issues.</description>
	<lastBuildDate>Wed, 04 Jan 2012 19:36:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Best Programming Practices #1 &#8211; multiple files</title>
		<link>http://nmpconsulting.com/blog/2009/12/29/best-programming-practices-1-multiple-files/</link>
		<comments>http://nmpconsulting.com/blog/2009/12/29/best-programming-practices-1-multiple-files/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 15:19:54 +0000</pubDate>
		<dc:creator>Chris Sunami</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[best programming practices #1]]></category>

		<guid isPermaLink="false">http://nmpconsulting.com/blog/?p=113</guid>
		<description><![CDATA[When I first started out as a programmer, I didn&#8217;t have much of a concept of best programming practices. If anything, I saw them as barriers in the way of doing what I really wanted to do. And although there are plenty of people on the web willing to yell at you when you don&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>When I first started out as a programmer, I didn&#8217;t have much of a concept of best programming practices.  If anything, I saw them as barriers in the way of doing what I really wanted to do.  And although there are plenty of people on the web willing to yell at you when you don&#8217;t follow good programming practices, there aren&#8217;t so many good explanations for beginners on what makes those practices good.  So this is the start of a series of quick tips on good programming practices and what makes them good.</p>
<p><strong>Tip #1: Divide your program up into multiple files.</strong></p>
<p>This used to drive me crazy when I first started as a programmer.  I would go in to work on a program and find five hundred separate little files, which would force me to hunt laboriously through them in order to find what I wanted.  I disliked this practice so much, I would often rewrite other people&#8217;s programs to put all the little files into one big one.  But guess what?  There were good reasons behind it all:</p>
<ul>
<li>Debugging:  If something goes wrong with your program &#8211;and it will&#8211; it&#8217;s much easier to disable one included file at a time then to search through a single massive program.</li>
<li>Reusability: Some portions of your code will be used over and over again, either within the same program or in a wholly separate project.  Save that code as a separate file, and you can use it anywhere, no cutting and pasting involved.</li>
<li>Structure:  A properly named and organized system of subdirectories can make the organization of your program clear at a glance.</li>
</ul>
<p>Of course, the key to making this tip work for you is organization.  It isn&#8217;t helpful at all to look through five hundred mysteriously named and ordered subroutines.  But if each separate file has a name that clearly identifies what it does, and is placed in a folder with other similar files, it eliminates a lot of the fruitless searching.</p>
]]></content:encoded>
			<wfw:commentRss>http://nmpconsulting.com/blog/2009/12/29/best-programming-practices-1-multiple-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

