<?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/"
		>
<channel>
	<title>Comments on: 3 Technology Components to Learn in 2010</title>
	<atom:link href="http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/</link>
	<description>Adventures in Programming</description>
	<lastBuildDate>Wed, 10 Mar 2010 10:54:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Justin</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9697</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 18 Jan 2010 21:06:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9697</guid>
		<description>Dave, I agree 100%.  One of the things I&#039;m looking forward to in using Compass/Sass is spending less time building the basic skeleton structure of a site and more time understanding _why_ a particular structure works.

Unfortunately, right now, I spend probably 90% of my time in CSS building up the basics to work in Chrome/Firefox, and then 10% trying to run around fixing small bugs/quirks.  I&#039;m hoping to leverage Sass to drastically cut down that 90% so that I can spend more time trying to understand why those small bugs/quirks are appearing in the first place (and how to fix them in such a way that I&#039;m not just applying a band-aid).

Nice blog, by the way.  I just subscribed. :)</description>
		<content:encoded><![CDATA[<p>Dave, I agree 100%.  One of the things I&#8217;m looking forward to in using Compass/Sass is spending less time building the basic skeleton structure of a site and more time understanding _why_ a particular structure works.</p>
<p>Unfortunately, right now, I spend probably 90% of my time in CSS building up the basics to work in Chrome/Firefox, and then 10% trying to run around fixing small bugs/quirks.  I&#8217;m hoping to leverage Sass to drastically cut down that 90% so that I can spend more time trying to understand why those small bugs/quirks are appearing in the first place (and how to fix them in such a way that I&#8217;m not just applying a band-aid).</p>
<p>Nice blog, by the way.  I just subscribed. <img src='http://www.justinrhinesmith.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Mosher</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9695</link>
		<dc:creator>Dave Mosher</dc:creator>
		<pubDate>Mon, 18 Jan 2010 19:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9695</guid>
		<description>Compass and SASS _can_ help you to abstract away browser rendering quirks but that doesn&#039;t mean you shouldn&#039;t take the time to understand why the quirks exist in the first place. Understanding things a few levels below the abstraction is a core characteristic of being a good developer :)

If you dig a little further into Compass/SASS you&#039;ll find the true power lies in the ability it gives you to truly separate the presentation layer from the structure layer; that is: separating your HTML from your CSS. When your HTML is purged of presentational classnames and ID&#039;s you preserve the life of your markup by making a clean separation between style and structure. Simply put, using SASS allows developers to code using patterns that enable you to swap out the style layer the way that CSS was intended to. You _can_ do this with pure CSS but Compass and SASS make this far easier with abstractions, mixins and variables.</description>
		<content:encoded><![CDATA[<p>Compass and SASS _can_ help you to abstract away browser rendering quirks but that doesn&#8217;t mean you shouldn&#8217;t take the time to understand why the quirks exist in the first place. Understanding things a few levels below the abstraction is a core characteristic of being a good developer <img src='http://www.justinrhinesmith.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>If you dig a little further into Compass/SASS you&#8217;ll find the true power lies in the ability it gives you to truly separate the presentation layer from the structure layer; that is: separating your HTML from your CSS. When your HTML is purged of presentational classnames and ID&#8217;s you preserve the life of your markup by making a clean separation between style and structure. Simply put, using SASS allows developers to code using patterns that enable you to swap out the style layer the way that CSS was intended to. You _can_ do this with pure CSS but Compass and SASS make this far easier with abstractions, mixins and variables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9694</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 18 Jan 2010 19:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9694</guid>
		<description>Yes, I do!

Unfortunately, nobody bothered to tell me that &quot;having a blog&quot; and &quot;writing a blog&quot; are two different things.  I assumed that by simply throwing up a blog engine, it would magically start filling up with interesting and relevant postings. :)</description>
		<content:encoded><![CDATA[<p>Yes, I do!</p>
<p>Unfortunately, nobody bothered to tell me that &#8220;having a blog&#8221; and &#8220;writing a blog&#8221; are two different things.  I assumed that by simply throwing up a blog engine, it would magically start filling up with interesting and relevant postings. <img src='http://www.justinrhinesmith.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9693</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 18 Jan 2010 17:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9693</guid>
		<description>Hey. You&#039;ve got a blog! Cool.</description>
		<content:encoded><![CDATA[<p>Hey. You&#8217;ve got a blog! Cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9691</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 18 Jan 2010 14:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9691</guid>
		<description>Yes, I&#039;m still mostly developing on Windows, with the main reason being that I&#039;m still much more comfortable with Windows over Linux, and I haven&#039;t yet been able to justify the purchase of a Mac (though that day is eventually coming -- I can feel it).

In terms of CC.rb, honestly, the things that I miss most from CC.NET are the robust documentation and the community.  Sadly, unless I&#039;m missing something, both of those things seem to be missing from CC.rb.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;m still mostly developing on Windows, with the main reason being that I&#8217;m still much more comfortable with Windows over Linux, and I haven&#8217;t yet been able to justify the purchase of a Mac (though that day is eventually coming &#8212; I can feel it).</p>
<p>In terms of CC.rb, honestly, the things that I miss most from CC.NET are the robust documentation and the community.  Sadly, unless I&#8217;m missing something, both of those things seem to be missing from CC.rb.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sidu</title>
		<link>http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/comment-page-1/#comment-9657</link>
		<dc:creator>Sidu</dc:creator>
		<pubDate>Sat, 16 Jan 2010 14:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.justinrhinesmith.com/blog/2010/01/03/3-technology-components-to-learn-in-2010/#comment-9657</guid>
		<description>Sadly, the Ruby world still hasn&#039;t caught up with the Java world when it comes to IDE support. Other than that, all is good. It seems from your post that you&#039;re actively developing on Windows. Any particular reason why  (or did I musunderstand)?

For CC.rb, what features were you looking for that CC.NET has? (I have exactly one commit to both, but still, maybe I can help ;))</description>
		<content:encoded><![CDATA[<p>Sadly, the Ruby world still hasn&#8217;t caught up with the Java world when it comes to IDE support. Other than that, all is good. It seems from your post that you&#8217;re actively developing on Windows. Any particular reason why  (or did I musunderstand)?</p>
<p>For CC.rb, what features were you looking for that CC.NET has? (I have exactly one commit to both, but still, maybe I can help <img src='http://www.justinrhinesmith.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
</channel>
</rss>
