<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Web Application Primer - Introduction</title>
	<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/</link>
	<description>ArcStone employees / contractors practicing Internet alchemy - translating tech into vision and vision into tech....</description>
	<pubDate>Tue, 06 Jan 2009 07:36:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Jess Louwagie</title>
		<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-2</link>
		<author>Jess Louwagie</author>
		<pubDate>Tue, 20 Mar 2007 17:07:54 +0000</pubDate>
		<guid>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-2</guid>
					<description>I challenge your point #1 and propose that #4 may be the most important part :)</description>
		<content:encoded><![CDATA[<p>I challenge your point #1 and propose that #4 may be the most important part <img src='http://www.technologytranslated.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: dcarnes</title>
		<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-3</link>
		<author>dcarnes</author>
		<pubDate>Wed, 21 Mar 2007 13:13:08 +0000</pubDate>
		<guid>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-3</guid>
					<description>I actually agree with Jess about the view - and I don't think he disagrees 'cause he's a designer and you're a coder - he may be onto something.  Isn't the utility, the usability the most important part?  When thinking about a web application the output and desired behavior is the starting point - then the implementation, database, code, etc. follows.  We talk about and work a lot with blue printing web apps - is this part of the model?

On another note - a question - are there any great web sites that have no database, controllers, etc?</description>
		<content:encoded><![CDATA[<p>I actually agree with Jess about the view - and I don&#8217;t think he disagrees &#8217;cause he&#8217;s a designer and you&#8217;re a coder - he may be onto something.  Isn&#8217;t the utility, the usability the most important part?  When thinking about a web application the output and desired behavior is the starting point - then the implementation, database, code, etc. follows.  We talk about and work a lot with blue printing web apps - is this part of the model?</p>
<p>On another note - a question - are there any great web sites that have no database, controllers, etc?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Austin Smith</title>
		<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-5</link>
		<author>Austin Smith</author>
		<pubDate>Tue, 27 Mar 2007 05:25:36 +0000</pubDate>
		<guid>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-5</guid>
					<description>Usability and even interface should be organic in a web application from the model up and when you talk about concern for these things, you should certainly not limit the scope of your concern to the presentation layer. While your point is of course is well taken that the view is what the user actually interacts with, a site built on a poor model is like a house built on a termite-ridden foundation. It may not kill you today, but you will pay for it eventually. An application built on a solid, normalized database will not only perform faster than one which is not, but the one with the normalized database will allow for the sort of graceful development in which each subsequent unfolds from the previous.</description>
		<content:encoded><![CDATA[<p>Usability and even interface should be organic in a web application from the model up and when you talk about concern for these things, you should certainly not limit the scope of your concern to the presentation layer. While your point is of course is well taken that the view is what the user actually interacts with, a site built on a poor model is like a house built on a termite-ridden foundation. It may not kill you today, but you will pay for it eventually. An application built on a solid, normalized database will not only perform faster than one which is not, but the one with the normalized database will allow for the sort of graceful development in which each subsequent unfolds from the previous.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bart Gottschalk</title>
		<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-7</link>
		<author>Bart Gottschalk</author>
		<pubDate>Tue, 03 Apr 2007 18:22:29 +0000</pubDate>
		<guid>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-7</guid>
					<description>Ah, the great debate about which layer or aspect of a web application is the most important.  I believe the layer that is most important depends on the requirements of the application.  Some business situations are driven by data (data base/model), some by integration (model) and others by the user experience (view).  If any of these considerations are not given appropriate attention (and appropriate is different for every project) the resulting application will not be able to grow and change to meet the ever changing demands of the owners and users.</description>
		<content:encoded><![CDATA[<p>Ah, the great debate about which layer or aspect of a web application is the most important.  I believe the layer that is most important depends on the requirements of the application.  Some business situations are driven by data (data base/model), some by integration (model) and others by the user experience (view).  If any of these considerations are not given appropriate attention (and appropriate is different for every project) the resulting application will not be able to grow and change to meet the ever changing demands of the owners and users.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Technology Translated &#187; Blog Archive &#187; Web Application Primer - The Dictator and the Database</title>
		<link>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-11</link>
		<author>Technology Translated &#187; Blog Archive &#187; Web Application Primer - The Dictator and the Database</author>
		<pubDate>Mon, 23 Apr 2007 03:49:06 +0000</pubDate>
		<guid>http://www.technologytranslated.com/2007/03/19/web-application-primer-part-1/#comment-11</guid>
					<description>[...] back to my unauthorized look into the seedy underbelly of a web application. (did you miss part one?) Today: the database. The model. The schema. The sick, twisted, gang of data that lurks beneath the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] back to my unauthorized look into the seedy underbelly of a web application. (did you miss part one?) Today: the database. The model. The schema. The sick, twisted, gang of data that lurks beneath the [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
