<?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: The Art and Zen of Writing CSS</title>
	<atom:link href="http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/</link>
	<description>Why not take my word for it?</description>
	<lastBuildDate>Wed, 07 Apr 2010 23:55:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Greg</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7534</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 07 Apr 2010 23:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7534</guid>
		<description>&lt;blockquote&gt;Utilize comments to define how CSS should be formatted and written for other authors.
Always count on the fact that someone other than you will probably work in this document at some point in time.
Utilize comments to organize your code into sections. Comments can effectively become a navigation system within your CSS document&lt;/blockquote&gt;
As a fledgling web desinger this was a very good read. Thank you very much for the input on CSS standards. Yes, I know that you weren&#039;t really commenting on standards specifically, but if these were standards life would be easier.. I am working on a project right now that is hard to know what the author was thinking and as a result have recoded huge portions of the site.Explination in the code would have been VERY helpful. Thanks.</description>
		<content:encoded><![CDATA[<blockquote><p>Utilize comments to define how CSS should be formatted and written for other authors.<br />
Always count on the fact that someone other than you will probably work in this document at some point in time.<br />
Utilize comments to organize your code into sections. Comments can effectively become a navigation system within your CSS document</p></blockquote>
<p>As a fledgling web desinger this was a very good read. Thank you very much for the input on CSS standards. Yes, I know that you weren&#8217;t really commenting on standards specifically, but if these were standards life would be easier.. I am working on a project right now that is hard to know what the author was thinking and as a result have recoded huge portions of the site.Explination in the code would have been VERY helpful. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TG Designer &#187; CSS Specificity And Inheritance</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7533</link>
		<dc:creator>TG Designer &#187; CSS Specificity And Inheritance</dc:creator>
		<pubDate>Wed, 07 Apr 2010 23:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7533</guid>
		<description>[...] good rule of thumb can be found in Jim Jeffers’ article, “The Art and Zen of Writing CSS”: Refactoring CSS selectors to be less specific is exponentially more difficult than simply [...]</description>
		<content:encoded><![CDATA[<p>[...] good rule of thumb can be found in Jim Jeffers’ article, “The Art and Zen of Writing CSS”: Refactoring CSS selectors to be less specific is exponentially more difficult than simply [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7529</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Wed, 07 Apr 2010 16:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7529</guid>
		<description>&lt;a href=&quot;http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/#comment-7528&quot; rel=&quot;nofollow&quot;&gt;@Nathan&lt;/a&gt;don&#039;t know where that wierd text at the front of the post came from...  user error i imagine</description>
		<content:encoded><![CDATA[<p><a href="http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/#comment-7528" rel="nofollow">@Nathan</a>don&#8217;t know where that wierd text at the front of the post came from&#8230;  user error i imagine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7528</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Wed, 07 Apr 2010 16:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7528</guid>
		<description>that will be eaTo add to the concept &quot;Lesson One: Only be Specific When You Need to Be.&quot;I see a lot of people over-specifying widths when they should not.  Like on your average block element - don&#039;t specify its width if you want it to take up the entire width of its container.That way, if you ever change the parent container&#039;s width the block elements with unspecified widths it automatically adjust properly.You&#039;re also free to apply margins &amp; padding to a block element that hasn&#039;t had its width specified and you&#039;ll get the desired result.  Put 20px padding on an unspecified width block element and it&#039;ll fill its container and have nice padding.  If your width would have been specified, you would have had to subtract your padding from the container&#039;s width to get the proper size.Long story short: don&#039;t specify widths unless you need to.  Your block elements will behave more like you would probably like them to.</description>
		<content:encoded><![CDATA[<p>that will be eaTo add to the concept &#8220;Lesson One: Only be Specific When You Need to Be.&#8221;I see a lot of people over-specifying widths when they should not.  Like on your average block element &#8211; don&#8217;t specify its width if you want it to take up the entire width of its container.That way, if you ever change the parent container&#8217;s width the block elements with unspecified widths it automatically adjust properly.You&#8217;re also free to apply margins &amp; padding to a block element that hasn&#8217;t had its width specified and you&#8217;ll get the desired result.  Put 20px padding on an unspecified width block element and it&#8217;ll fill its container and have nice padding.  If your width would have been specified, you would have had to subtract your padding from the container&#8217;s width to get the proper size.Long story short: don&#8217;t specify widths unless you need to.  Your block elements will behave more like you would probably like them to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS Specificity And Inheritance &#124; Web Design Cool</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7526</link>
		<dc:creator>CSS Specificity And Inheritance &#124; Web Design Cool</dc:creator>
		<pubDate>Wed, 07 Apr 2010 15:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7526</guid>
		<description>[...] good rule of thumb can be found in Jim Jeffers’ article, “The Art and Zen of Writing CSS”: Refactoring CSS selectors to be less specific is exponentially more difficult than simply [...]</description>
		<content:encoded><![CDATA[<p>[...] good rule of thumb can be found in Jim Jeffers’ article, “The Art and Zen of Writing CSS”: Refactoring CSS selectors to be less specific is exponentially more difficult than simply [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS Specificity And Inheritance - Smashing Magazine</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7522</link>
		<dc:creator>CSS Specificity And Inheritance - Smashing Magazine</dc:creator>
		<pubDate>Wed, 07 Apr 2010 14:36:10 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7522</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Dev Tutorials 1# &#124; Booto'Blog</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7516</link>
		<dc:creator>Web Dev Tutorials 1# &#124; Booto'Blog</dc:creator>
		<pubDate>Tue, 06 Apr 2010 00:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7516</guid>
		<description>[...] The Art and Zen of Writing CSS By Jim Jeffers, March 7th, 2010 Site: DontTrustThisGuy [...]</description>
		<content:encoded><![CDATA[<p>[...] The Art and Zen of Writing CSS By Jim Jeffers, March 7th, 2010 Site: DontTrustThisGuy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pol Moneys</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7485</link>
		<dc:creator>Pol Moneys</dc:creator>
		<pubDate>Fri, 02 Apr 2010 23:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7485</guid>
		<description>Thanks for sharing. nothing new but classy.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing. nothing new but classy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ulyses</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7483</link>
		<dc:creator>Ulyses</dc:creator>
		<pubDate>Fri, 02 Apr 2010 21:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7483</guid>
		<description>I agree with (some of) what you say, I learn (some of what) you are so gentlemen to share with us.I don&#039;t (completly) agree on the styling for CSS rules. This is probably the most important thing when writing CSS. Later on, you can be misslead by the way you write it down earlier, so I believe in a semnatic aproach rather then a alphabetized one.I even made a rule, I &quot;named a wizard&quot; (like in focus-acitve...) to help with that, and I believe in more then a rule per line.</description>
		<content:encoded><![CDATA[<p>I agree with (some of) what you say, I learn (some of what) you are so gentlemen to share with us.I don&#8217;t (completly) agree on the styling for CSS rules. This is probably the most important thing when writing CSS. Later on, you can be misslead by the way you write it down earlier, so I believe in a semnatic aproach rather then a alphabetized one.I even made a rule, I &#8220;named a wizard&#8221; (like in focus-acitve&#8230;) to help with that, and I believe in more then a rule per line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Atkin</title>
		<link>http://donttrustthisguy.com/2010/03/07/the-art-and-zen-of-writing-css/comment-page-1/#comment-7321</link>
		<dc:creator>Ben Atkin</dc:creator>
		<pubDate>Sun, 21 Mar 2010 09:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://donttrustthisguy.com/?p=391#comment-7321</guid>
		<description>&lt;blockquote&gt;The reality is if we don’t use CSS resets we implement them in a much more difficult manner.&lt;/blockquote&gt;
When I read this, I was instantly reminded of &lt;a href=&quot;http://en.wikipedia.org/wiki/Greenspun&#039;s_Tenth_Rule&quot; rel=&quot;nofollow&quot;&gt;Greenspun&#039;s Tenth Rule&lt;/a&gt;:&lt;blockquote&gt;Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.&lt;/blockquote&gt;I&#039;m going to start insisting on using resets. There&#039;s science to back me up!(This is not to say that other people can&#039;t be efficient working without resets. But I know it&#039;s more trouble than it&#039;s worth for me.)</description>
		<content:encoded><![CDATA[<blockquote><p>The reality is if we don’t use CSS resets we implement them in a much more difficult manner.</p></blockquote>
<p>When I read this, I was instantly reminded of <a href="http://en.wikipedia.org/wiki/Greenspun's_Tenth_Rule" rel="nofollow">Greenspun&#8217;s Tenth Rule</a>:<br />
<blockquote>Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.</p></blockquote>
<p>I&#8217;m going to start insisting on using resets. There&#8217;s science to back me up!(This is not to say that other people can&#8217;t be efficient working without resets. But I know it&#8217;s more trouble than it&#8217;s worth for me.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
