<?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://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html"/>
	<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://net.tutsplus.com/tutorials/javascript-ajax/test-driven-javascript-development-in-practice/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html">
    <title>Don't Make Your Code &quot;More Testable&quot;</title>
    <dc:date>2012-07-16T15:37:47+00:00</dc:date>
    <link>http://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In some ways I'm very excited that the Ruby community seems to have taken up the "Mocking/OO flag" so to speak lately. Most of the Ruby conferences seem to have talks around "Object Oriented Rails", "Isolated Unit Tests", and things like the "SOLID Design Principles". And even more exciting for me is that I see more and more people referencing the Growing Object Oriented Software Guided By Tests book. I think these are all great steps for us towards producing more maintainable software over time.

]]></description>
<dc:subject>ruby testing tdd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:48c8ffccfd9c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:tdd"/>
</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://net.tutsplus.com/tutorials/javascript-ajax/test-driven-javascript-development-in-practice/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader">
    <title>Test-Driven JavaScript Development in Practice | Nettuts+</title>
    <dc:date>2010-11-16T15:54:08+00:00</dc:date>
    <link>http://net.tutsplus.com/tutorials/javascript-ajax/test-driven-javascript-development-in-practice/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[TDD is an iterative development process where each iteration starts by writing a test which forms a part of the specification we are implementing. The short iterations allow for more instant feedback on the code we are writing, and bad design decisions are easier to catch. By writing the tests prior to any production code, good unit test coverage comes with the territory, but that is merely a welcome side-effect.
]]></description>
<dc:subject>javascript tdd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:a2d2988159af/</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:Bag></taxo:topics>
</item>
</rdf:RDF>