<?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; Software Engineering</title>
	<atom:link href="http://www.icodebd.com/tag/software-engineering/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>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 2.495 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-01-28 13:23:15 -->
<!-- Compression = gzip -->
