<?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: On why HTML and XML have succeeded, and the lessons therein</title>
	<atom:link href="http://maxtempleton.wordpress.com/2008/03/19/on-why-html-and-xml-succeeded-and-the-lessons-therein/feed/" rel="self" type="application/rss+xml" />
	<link>http://maxtempleton.wordpress.com/2008/03/19/on-why-html-and-xml-succeeded-and-the-lessons-therein/</link>
	<description>Max Templeton on software design and related topics</description>
	<lastBuildDate>Mon, 30 Nov 2009 20:22:47 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arnoud</title>
		<link>http://maxtempleton.wordpress.com/2008/03/19/on-why-html-and-xml-succeeded-and-the-lessons-therein/#comment-38</link>
		<dc:creator>Arnoud</dc:creator>
		<pubDate>Mon, 30 Nov 2009 20:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://maxtempleton.wordpress.com/?p=13#comment-38</guid>
		<description>Tolerance for error is both the beauty and the beast.

The beauty is indeed the ease of entry through almost instant gratification, which is critical. The beast is that erroneous progress will lead to a point where there is no more sustainable growth possible without a significant amount of unlearning of bad habits.

The mastery of bringing on new technology is understanding when the beauty is about to become a beast, and being able to apply some retro-active rigor at that stage.

Retro-active application of stricter development rules presents issues when not all individuals in an organization have enough skills to make such a step.


The cascading style sheets (CSS) progression mentioned is a good example. Applying cascading style sheets on top of HTML containing bad habits will progress slowly, and possibly halt CSS adoption due to the lack of timely successes. An effort will have to be made to refactor HTML to instill proper use of in-line style attributes, span and div, and so on.

The skill progression with cascading style sheets will be rewarding as described, if all HTML developers follow the necessary rigor.</description>
		<content:encoded><![CDATA[<p>Tolerance for error is both the beauty and the beast.</p>
<p>The beauty is indeed the ease of entry through almost instant gratification, which is critical. The beast is that erroneous progress will lead to a point where there is no more sustainable growth possible without a significant amount of unlearning of bad habits.</p>
<p>The mastery of bringing on new technology is understanding when the beauty is about to become a beast, and being able to apply some retro-active rigor at that stage.</p>
<p>Retro-active application of stricter development rules presents issues when not all individuals in an organization have enough skills to make such a step.</p>
<p>The cascading style sheets (CSS) progression mentioned is a good example. Applying cascading style sheets on top of HTML containing bad habits will progress slowly, and possibly halt CSS adoption due to the lack of timely successes. An effort will have to be made to refactor HTML to instill proper use of in-line style attributes, span and div, and so on.</p>
<p>The skill progression with cascading style sheets will be rewarding as described, if all HTML developers follow the necessary rigor.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
