<?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>Engineering Institute &#187; programmers</title>
	<atom:link href="http://www.etoinstitute.org/tag/programmers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.etoinstitute.org</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 02:18:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Career Paths for Programmers By John Bennett, Jr.</title>
		<link>http://www.etoinstitute.org/career-paths-for-programmers-by-john-bennett-jr/</link>
		<comments>http://www.etoinstitute.org/career-paths-for-programmers-by-john-bennett-jr/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 04:19:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[business analyst]]></category>
		<category><![CDATA[career paths]]></category>
		<category><![CDATA[computer programmer]]></category>
		<category><![CDATA[employment outlook]]></category>
		<category><![CDATA[john bennett]]></category>
		<category><![CDATA[programmers]]></category>
		<category><![CDATA[systems analyst]]></category>
		<category><![CDATA[systems architect]]></category>

		<guid isPermaLink="false">http://www.etoinstitute.org/career-paths-for-programmers-by-john-bennett-jr/</guid>
		<description><![CDATA[The key to maintaining a good employment outlook in IT, it seems, is to move out of programming and up into more business-oriented IT positions such as systems analyst, business analyst, project manager, or systems architect. However, a computer programmer can&#8217;t just decide to become a systems analyst or project manager overnight.Click here for the [...]]]></description>
			<content:encoded><![CDATA[<p>The key to maintaining a good employment outlook in IT, it seems, is to move out of programming and up into more business-oriented IT positions such as systems analyst, business analyst, project manager, or systems architect. However, a computer programmer can&#8217;t just decide to become a systems analyst or project manager overnight.<br/><a href="http://www.developerdotstar.com/mag/articles/programmer_career.html" />Click here for the full article.<br />
    <a href="http://www.developerdotstar.com/mag/articles/programmer_career.html">Read More</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.etoinstitute.org/career-paths-for-programmers-by-john-bennett-jr/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interface Oriented Design Book Excerpt: Inheritance and Interfaces (Chapter 5) By Ken Pugh</title>
		<link>http://www.etoinstitute.org/interface-oriented-design-book-excerpt-inheritance-and-interfaces-chapter-5-by-ken-pugh/</link>
		<comments>http://www.etoinstitute.org/interface-oriented-design-book-excerpt-inheritance-and-interfaces-chapter-5-by-ken-pugh/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 04:19:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[book excerpt]]></category>
		<category><![CDATA[commonality]]></category>
		<category><![CDATA[excerpt from]]></category>
		<category><![CDATA[inheritance hierarchy]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[object oriented programming]]></category>
		<category><![CDATA[oriented design]]></category>
		<category><![CDATA[programmers]]></category>

		<guid isPermaLink="false">http://www.etoinstitute.org/interface-oriented-design-book-excerpt-inheritance-and-interfaces-chapter-5-by-ken-pugh/</guid>
		<description><![CDATA[Finding commonality among classes makes for effective object-oriented programming. Often, programmers express that commonality using an inheritance hierarchy, since that is one of the first concepts taught in object-oriented programming. We&#8217;re going to go to the other extreme in this chapter to explore the difference between using inheritance and using interfaces. An excerpt from Interface [...]]]></description>
			<content:encoded><![CDATA[<p>Finding commonality among classes makes for effective object-oriented programming. Often, programmers express that commonality using an inheritance hierarchy, since that is one of the first concepts taught in object-oriented programming. We&#8217;re going to go to the other extreme in this chapter to explore the difference between using inheritance and using interfaces. An excerpt from Interface Oriented Design.<br/><a href="http://www.developerdotstar.com/mag/articles/pugh_interface_oriented.html" />Click here for the full article.<br />
    <a href="http://www.developerdotstar.com/mag/articles/pugh_interface_oriented.html">Read More</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.etoinstitute.org/interface-oriented-design-book-excerpt-inheritance-and-interfaces-chapter-5-by-ken-pugh/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

