<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: To become a masterful internet application engineer?</title>
	<atom:link href="http://blog.gahooa.com/2009/05/12/to-become-a-masterful-internet-application-engineer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gahooa.com/2009/05/12/to-become-a-masterful-internet-application-engineer/</link>
	<description>Thoughts on Life, Engineering, Technology, Business, and more...</description>
	<lastBuildDate>Mon, 25 Jan 2010 04:08:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Andrew Bidochko</title>
		<link>http://blog.gahooa.com/2009/05/12/to-become-a-masterful-internet-application-engineer/#comment-66</link>
		<dc:creator>Andrew Bidochko</dc:creator>
		<pubDate>Mon, 15 Jun 2009 14:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gahooa.com/?p=140#comment-66</guid>
		<description>Number of languages or technologies doesn’t matter. 
Internet application engineer should know all major aspects of web applications architecture (http, web security, browser’s model, web frameworks, best practices, etc) and general principles of software design and architecture (OOP, design patterns, etc) . That’s enough to call a person a ‘web app engeener’. Knowledge of JS, CSS, HTML, PHP, Python, etc  might be helpful but it doesn’t make you an engineer.</description>
		<content:encoded><![CDATA[<p>Number of languages or technologies doesn’t matter.<br />
Internet application engineer should know all major aspects of web applications architecture (http, web security, browser’s model, web frameworks, best practices, etc) and general principles of software design and architecture (OOP, design patterns, etc) . That’s enough to call a person a ‘web app engeener’. Knowledge of JS, CSS, HTML, PHP, Python, etc  might be helpful but it doesn’t make you an engineer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis Fisher</title>
		<link>http://blog.gahooa.com/2009/05/12/to-become-a-masterful-internet-application-engineer/#comment-37</link>
		<dc:creator>Travis Fisher</dc:creator>
		<pubDate>Wed, 13 May 2009 18:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gahooa.com/?p=140#comment-37</guid>
		<description>I think you hit the necessities for any web developer with that &quot;base&quot; list.

As for server-side languages, I think people get too caught up with &quot;you need to use X language, or you suck&quot;. I, personally, hate ColdFusion, but I&#039;ve seen some good web apps come from that language.

It&#039;s all what you make of the tools you know.</description>
		<content:encoded><![CDATA[<p>I think you hit the necessities for any web developer with that &#8220;base&#8221; list.</p>
<p>As for server-side languages, I think people get too caught up with &#8220;you need to use X language, or you suck&#8221;. I, personally, hate ColdFusion, but I&#8217;ve seen some good web apps come from that language.</p>
<p>It&#8217;s all what you make of the tools you know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Garber</title>
		<link>http://blog.gahooa.com/2009/05/12/to-become-a-masterful-internet-application-engineer/#comment-36</link>
		<dc:creator>Jason Garber</dc:creator>
		<pubDate>Tue, 12 May 2009 16:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gahooa.com/?p=140#comment-36</guid>
		<description>It depends on the stack... 

User Interface: 
HTML, XHTML, CSS, Javascript, JSON, AJAX, XML, HTTP, SSL...</description>
		<content:encoded><![CDATA[<p>It depends on the stack&#8230; </p>
<p>User Interface:<br />
HTML, XHTML, CSS, Javascript, JSON, AJAX, XML, HTTP, SSL&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
