<?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>ICode , Bangladesh &#187; naming convention</title>
	<atom:link href="http://www.icodebd.com/tag/naming-convention/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.icodebd.com</link>
	<description>Power and Confidence in code</description>
	<lastBuildDate>Sat, 07 Jan 2012 13:55:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>Class oriented programming</title>
		<link>http://www.icodebd.com/class-oriented-programming/</link>
		<comments>http://www.icodebd.com/class-oriented-programming/#comments</comments>
		<pubDate>Tue, 24 May 2011 12:03:42 +0000</pubDate>
		<dc:creator>AdhocMaster</dc:creator>
				<category><![CDATA[Basic Programming Logic]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[code architecture]]></category>
		<category><![CDATA[naming convention]]></category>
		<category><![CDATA[naming convention in software engineering]]></category>
		<category><![CDATA[well-managed code]]></category>

		<guid isPermaLink="false">http://www.icodebd.com/?p=401</guid>
		<description><![CDATA[©icode.com : For well-managed small projects, class-oriented programming works very well, especially for scripting platforms like PHP, where you actually never save any object for later use. Here goes my plan of class-oriented development: 1. Create classes for every Entity. So if you have entities like &#8216;category&#8217;, &#8216;person&#8217;, &#8216;product&#8217;, etc, you need to create classes [...]]]></description>
		<wfw:commentRss>http://www.icodebd.com/class-oriented-programming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Naming Convention Part 3: Ugliest Varible Names</title>
		<link>http://www.icodebd.com/naming-convention-part-3-ugliest-varible-names/</link>
		<comments>http://www.icodebd.com/naming-convention-part-3-ugliest-varible-names/#comments</comments>
		<pubDate>Sun, 23 May 2010 20:15:16 +0000</pubDate>
		<dc:creator>AdhocMaster</dc:creator>
				<category><![CDATA[common mistakes]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[ambiguous variable names]]></category>
		<category><![CDATA[naming convention]]></category>
		<category><![CDATA[naming convention in software engineering]]></category>
		<category><![CDATA[variable naming]]></category>

		<guid isPermaLink="false">http://www.icodebd.com/?p=179</guid>
		<description><![CDATA[©icode.com : Please read my previous article Naming Convention Part 2: Purpose of a Variable before reading this one. Here goes two ugliest variable names which are most widely used, especially in Database applications: row and results with aliases like rows, res, result, etc. We do it to code very fast. This type of generic [...]]]></description>
		<wfw:commentRss>http://www.icodebd.com/naming-convention-part-3-ugliest-varible-names/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Naming Convention Part 2: Purpose of a Variable</title>
		<link>http://www.icodebd.com/naming-convention-part-2-purpose-of-a-variable/</link>
		<comments>http://www.icodebd.com/naming-convention-part-2-purpose-of-a-variable/#comments</comments>
		<pubDate>Tue, 04 May 2010 08:04:04 +0000</pubDate>
		<dc:creator>AdhocMaster</dc:creator>
				<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[ambiguity]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[literate proramming]]></category>
		<category><![CDATA[naming convention]]></category>
		<category><![CDATA[purpose of variable]]></category>
		<category><![CDATA[variable naming]]></category>
		<category><![CDATA[wel-managed code]]></category>

		<guid isPermaLink="false">http://www.icodebd.com/?p=157</guid>
		<description><![CDATA[©icode.com : First part: What is a variable actually? Simply it&#8217;s a container that has a name. The best practice creating and using variable is to stick a name to a single purpose only. Say we have some chemicals stored in some bottles and we put a tag on each bottle with the name of [...]]]></description>
		<wfw:commentRss>http://www.icodebd.com/naming-convention-part-2-purpose-of-a-variable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Naming Conventions and Design Patterns</title>
		<link>http://www.icodebd.com/naming-conventions-and-design-patterns/</link>
		<comments>http://www.icodebd.com/naming-conventions-and-design-patterns/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 14:22:34 +0000</pubDate>
		<dc:creator>AdhocMaster</dc:creator>
				<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[design patterns]]></category>
		<category><![CDATA[naming convention]]></category>

		<guid isPermaLink="false">http://www.icodebd.com/?p=126</guid>
		<description><![CDATA[©icode.com : Overall: 1. All the variable names are in camel notation (aName, totalAmount). 2. All the attribute names are in camel notation. That goes for forms, entity atrribute names, entity names. Say you have a entity called &#8216;person&#8217; and it has some attributes, then we choose the attribute names this way &#8211; name, dateOfBirth, [...]]]></description>
		<wfw:commentRss>http://www.icodebd.com/naming-conventions-and-design-patterns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 1.303 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-01-28 13:20:47 -->
<!-- Compression = gzip -->
