<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jpcody)</title>
    <link>https://pinboard.in/u:jpcody/public/</link>
    <description>recent bookmarks from jpcody</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://engineering.appfolio.com/2012/11/16/css-architecture/"/>
	<rdf:li rdf:resource="http://nicolasgallagher.com/about-html-semantics-front-end-architecture/"/>
	<rdf:li rdf:resource="https://github.com/csswizardry/CSS-Guidelines/blob/master/CSS%20Guidelines.md"/>
	<rdf:li rdf:resource="http://www.jbarnette.com/2009/09/07/boring-things-first.html"/>
	<rdf:li rdf:resource="http://chrismdp.github.com/2012/02/on-coding-defensively/"/>
	<rdf:li rdf:resource="http://yellowshoe.com.au/standards/"/>
	<rdf:li rdf:resource="http://daringfireball.net/2010/12/title_junk"/>
	<rdf:li rdf:resource="http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript"/>
	<rdf:li rdf:resource="http://encosia.com/2010/08/18/dont-let-jquerys-document-ready-slow-you-down/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://engineering.appfolio.com/2012/11/16/css-architecture/">
    <title>CSS Architecture | Appfolio Engineering</title>
    <dc:date>2013-05-12T03:08:22+00:00</dc:date>
    <link>http://engineering.appfolio.com/2012/11/16/css-architecture/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[To many Web developers, being good at CSS means you can take a visual mock-up and replicate it perfectly in code. You don’t use tables, and you pride yourself on using as few images as possible. If you’re really good, you use the latest and greatest techniques like media queries, transitions and transforms. While all this is certainly true of good CSS developers, there’s an entirely separate side to CSS that rarely gets mentioned when assessing one’s skill.

]]></description>
<dc:subject>css bestpractices architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:dbd80f86712c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nicolasgallagher.com/about-html-semantics-front-end-architecture/">
    <title>About HTML semantics and front-end architecture – Nicolas Gallagher</title>
    <dc:date>2012-03-26T02:18:28+00:00</dc:date>
    <link>http://nicolasgallagher.com/about-html-semantics-front-end-architecture/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[A collection of thoughts, experiences, ideas that I like, and ideas that I have been experimenting with over the last year. It covers HTML semantics, components and approaches to front-end architecture, class naming patterns, and HTTP compression.

]]></description>
<dc:subject>css bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:fcb6469477d5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/csswizardry/CSS-Guidelines/blob/master/CSS%20Guidelines.md">
    <title>CSS-Guidelines/CSS Guidelines.md at master · csswizardry/CSS-Guidelines</title>
    <dc:date>2012-03-26T02:03:07+00:00</dc:date>
    <link>https://github.com/csswizardry/CSS-Guidelines/blob/master/CSS%20Guidelines.md</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[General CSS notes, advice and guidelines
]]></description>
<dc:subject>bestpractices css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:8c1a9a59a55f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jbarnette.com/2009/09/07/boring-things-first.html">
    <title>“Boring Things First” by John Barnette</title>
    <dc:date>2012-03-26T01:32:24+00:00</dc:date>
    <link>http://www.jbarnette.com/2009/09/07/boring-things-first.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Yeah, yeah. You’re agile. You always test first, you work in tight iterations, you have YAGNI tattooed on your forehead. Good for you. Guess what? You’re building on sand. Do this stuff first:

]]></description>
<dc:subject>development bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:bc780fd9a656/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chrismdp.github.com/2012/02/on-coding-defensively/">
    <title>On coding defensively</title>
    <dc:date>2012-03-10T15:33:55+00:00</dc:date>
    <link>http://chrismdp.github.com/2012/02/on-coding-defensively/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[When writing code that will be used by others (and we do that 100% of the time, even if the other user is ourselves in a few weeks time), there’s a tricky balance to strike between being generous to the users of our code, and ensuring that they get the information they want to ensure they’re calling our code correctly. There are two coding maxims: “Be generous on input, and strict on output”, and “fail fast”, which we need to hold in tension. This post explores the trade-offs between the two.

]]></description>
<dc:subject>programming bestpractices ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:9101ff51c13e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yellowshoe.com.au/standards/">
    <title>Front end standards</title>
    <dc:date>2011-04-12T00:16:27+00:00</dc:date>
    <link>http://yellowshoe.com.au/standards/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This little book is to aid a shared understanding of front-end development best practice at PUP.

It's to help us deliver high quality content that works better, reaches more people - not only in today's browsers & devices, but in tomorrows.]]></description>
<dc:subject>standards bestpractices css styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ccd038f6ce89/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://daringfireball.net/2010/12/title_junk">
    <title>Daring Fireball: Title Junk</title>
    <dc:date>2010-12-21T00:32:45+00:00</dc:date>
    <link>http://daringfireball.net/2010/12/title_junk</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The recent hubbub about Delicious got me thinking about bookmarking in general, and brought to mind a long-standing irritation: poorly designed web page titles.

]]></description>
<dc:subject>seo usability bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ac6fb60da7e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:seo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript">
    <title>Jeff Dean's Ruby Blog - Tips for writing testable, maintainable page-specific javascript</title>
    <dc:date>2010-12-18T00:23:17+00:00</dc:date>
    <link>http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I've worked on several large Rails apps and seen at least a dozen javascript systems. In this post I'll describe a few techniques that I've seen that consistently make javascript easier to test and maintain. To those of you who write javascript more than I do, these might be old news, but it's taken me 4 years to learn them!]]></description>
<dc:subject>javascript tdd testing bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:baf4b0079667/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://encosia.com/2010/08/18/dont-let-jquerys-document-ready-slow-you-down/">
    <title>Don’t let jQuery’s $(document).ready() slow you down | Encosia</title>
    <dc:date>2010-08-19T15:56:31+00:00</dc:date>
    <link>http://encosia.com/2010/08/18/dont-let-jquerys-document-ready-slow-you-down/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[jQuery’s $(document).ready() event is something that you probably learned about in your earliest exposure to jQuery and then rarely thought about again. The way it abstracts away DOM timing issues is like a warm security blanket for code running in a variety of cold, harsh browser windows.
]]></description>
<dc:subject>javascript jquery documentready bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:530047bdcd6f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:documentready"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>