<?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: 5 most important things I learned in 5 years of front-end development</title>
	<atom:link href="http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/</link>
	<description>Get your web worker news fix</description>
	<lastBuildDate>Fri, 10 Feb 2012 21:12:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Best buy 13</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-139970</link>
		<dc:creator>Best buy 13</dc:creator>
		<pubDate>Sun, 05 Feb 2012 13:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-139970</guid>
		<description>Oh! Thanks for your post.</description>
		<content:encoded><![CDATA[<p>Oh! Thanks for your post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chai</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-100601</link>
		<dc:creator>chai</dc:creator>
		<pubDate>Tue, 20 Dec 2011 05:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-100601</guid>
		<description>thank good code.</description>
		<content:encoded><![CDATA[<p>thank good code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Widmann</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-9938</link>
		<dc:creator>Brett Widmann</dc:creator>
		<pubDate>Sat, 23 Oct 2010 22:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-9938</guid>
		<description>Thanks for the tips. It&#039;s nice to hear what other people have learned from their positions.</description>
		<content:encoded><![CDATA[<p>Thanks for the tips. It&#8217;s nice to hear what other people have learned from their positions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ralf57</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2773</link>
		<dc:creator>ralf57</dc:creator>
		<pubDate>Fri, 11 Sep 2009 07:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2773</guid>
		<description>CSS indenting is a non-existing issue, just use a code browser within your editor ;-)</description>
		<content:encoded><![CDATA[<p>CSS indenting is a non-existing issue, just use a code browser within your editor <img src='http://www.position-absolute.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Florent V.</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2651</link>
		<dc:creator>Florent V.</dc:creator>
		<pubDate>Fri, 04 Sep 2009 11:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2651</guid>
		<description>I would not add code formatting preferences to an advice article. There are quite a few different code formatting styles out there for CSS, each used by a lot of skilled front-end developers who could swear it&#039;s the best thing since sliced bread. You know what? No coding style is.

My coding style for CSS involves two levels of comments that work like titles (/* --- COMMENT --- */ and /* Comment */), one declaration per line with one indent, a hierarchical order of declaration by property (display, positioning, text, background), no hierarchical indentation. Is that better than yours? Certainly not. Yet my (small) company is going to standardize its coding style around that one because we need a common standard, my own is decent and i&#039;m the CSS expert.

The coding style is not important. What&#039;s good (in my opinion) is to have one and stick to it. So, when coding Python, we try to follow PEP8. It might not suit or taste all the time (i prefer tab characters over the recommended 4-space-indents, the line length restriction is a bit too strict…), but sticking to it most of the time helps everyone understand coworkers&#039; code.

I&#039;d say all your other pieces of advice are solid, but coding standards are mostly arbitrary.</description>
		<content:encoded><![CDATA[<p>I would not add code formatting preferences to an advice article. There are quite a few different code formatting styles out there for CSS, each used by a lot of skilled front-end developers who could swear it&#8217;s the best thing since sliced bread. You know what? No coding style is.</p>
<p>My coding style for CSS involves two levels of comments that work like titles (/* &#8212; COMMENT &#8212; */ and /* Comment */), one declaration per line with one indent, a hierarchical order of declaration by property (display, positioning, text, background), no hierarchical indentation. Is that better than yours? Certainly not. Yet my (small) company is going to standardize its coding style around that one because we need a common standard, my own is decent and i&#8217;m the CSS expert.</p>
<p>The coding style is not important. What&#8217;s good (in my opinion) is to have one and stick to it. So, when coding Python, we try to follow PEP8. It might not suit or taste all the time (i prefer tab characters over the recommended 4-space-indents, the line length restriction is a bit too strict…), but sticking to it most of the time helps everyone understand coworkers&#8217; code.</p>
<p>I&#8217;d say all your other pieces of advice are solid, but coding standards are mostly arbitrary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emptywalls</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2441</link>
		<dc:creator>emptywalls</dc:creator>
		<pubDate>Thu, 27 Aug 2009 23:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2441</guid>
		<description>I&#039;ll have to try the CSS indent trick, that looks great. You&#039;ll have to twist my arm to get me to try the &#039;minimize your CSS&#039; trick, but it makes sense.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll have to try the CSS indent trick, that looks great. You&#8217;ll have to twist my arm to get me to try the &#8216;minimize your CSS&#8217; trick, but it makes sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-08-20&#160;&#124;&#160;sashidhar.com</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2273</link>
		<dc:creator>links for 2009-08-20&#160;&#124;&#160;sashidhar.com</dc:creator>
		<pubDate>Thu, 20 Aug 2009 09:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2273</guid>
		<description>[...] 5 most important things I learned in 5 years of front-end development « Position Absolute (tags: css ui UX) [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 most important things I learned in 5 years of front-end development « Position Absolute (tags: css ui UX) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cedric Dugas</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2236</link>
		<dc:creator>Cedric Dugas</dc:creator>
		<pubDate>Tue, 18 Aug 2009 12:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2236</guid>
		<description>Interesting, I will have a look at Snook article</description>
		<content:encoded><![CDATA[<p>Interesting, I will have a look at Snook article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markive</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2232</link>
		<dc:creator>Markive</dc:creator>
		<pubDate>Tue, 18 Aug 2009 08:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2232</guid>
		<description>I agree with Kelly - Jonathon Snook recommended always coding CSS on one line so that you can quickly scan down the document for the required style. I heavily indent related styles aswell which helps and I make everyone I work with do the same and they soon see the benefits!

Love the site!

Cheers,
M</description>
		<content:encoded><![CDATA[<p>I agree with Kelly &#8211; Jonathon Snook recommended always coding CSS on one line so that you can quickly scan down the document for the required style. I heavily indent related styles aswell which helps and I make everyone I work with do the same and they soon see the benefits!</p>
<p>Love the site!</p>
<p>Cheers,<br />
M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://www.position-absolute.com/articles/5-most-important-things-i-learned-in-5-years-of-front-end-development/comment-page-1/#comment-2230</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Tue, 18 Aug 2009 03:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.position-absolute.com/?p=1429#comment-2230</guid>
		<description>I disagree about having your css indented. Properly formatted, the one-line method is far easier for me to read when scanning through copious amounts of code. It&#039;s definitely a matter of preference though, as I know other developers who are like you and prefer it your way.

For the record, I too have been told the legibility of my code sets my work apart.

Great article though! I love your site and check it regularly =)</description>
		<content:encoded><![CDATA[<p>I disagree about having your css indented. Properly formatted, the one-line method is far easier for me to read when scanning through copious amounts of code. It&#8217;s definitely a matter of preference though, as I know other developers who are like you and prefer it your way.</p>
<p>For the record, I too have been told the legibility of my code sets my work apart.</p>
<p>Great article though! I love your site and check it regularly =)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

