<?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 (Vaguery)</title>
    <link>https://pinboard.in/u:Vaguery/public/</link>
    <description>recent bookmarks from Vaguery</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://blog.orfjackal.net/2010/04/direct-and-indirect-effects-of-tdd.html"/>
	<rdf:li rdf:resource="http://codingdojo.org/cgi-bin/wiki.pl?KataFizzBuzz"/>
	<rdf:li rdf:resource="http://www.bitcetera.com/en/techblog/2009/05/27/mac-friendly-autotest/"/>
	<rdf:li rdf:resource="http://www.pathf.com/blogs/2009/05/rails-testing-frequently-asked-questions-the-non-code-version/"/>
	<rdf:li rdf:resource="http://fakeweb.rubyforge.org/"/>
	<rdf:li rdf:resource="http://xunitpatterns.com/Test%20Stub.html"/>
	<rdf:li rdf:resource="http://github.com/btakita/rr/tree/master"/>
	<rdf:li rdf:resource="http://www.claytonlz.com/index.php/2009/04/how-to-setup-rspec-cucumber-webrat-rcov-and-autotest-on-leopard/"/>
	<rdf:li rdf:resource="http://github.com/notahat/machinist/tree/master"/>
	<rdf:li rdf:resource="http://www.pathf.com/blogs/2009/03/using-cucumber-for-acceptance-testing/"/>
	<rdf:li rdf:resource="http://www.nomachetejuggling.com/2009/02/21/i-love-pair-programming/"/>
	<rdf:li rdf:resource="http://thoughtbot.com/projects/mile_marker"/>
	<rdf:li rdf:resource="http://giantrobots.thoughtbot.com/2009/2/20/mixing-cucumber-with-test-unit"/>
	<rdf:li rdf:resource="http://thoughtbot.com/projects/shoulda"/>
	<rdf:li rdf:resource="http://mir.aculo.us/2006/09/16/adventures-in-javascript-testing"/>
	<rdf:li rdf:resource="http://blog.objectmentor.com/articles/2008/11/27/the-truth-about-bdd"/>
	<rdf:li rdf:resource="http://ericholscher.com/tag/testing-series/"/>
	<rdf:li rdf:resource="http://rubyhoedown2008.confreaks.com/11-rick-bradley-flog-test-new.html"/>
	<rdf:li rdf:resource="http://www.voidspace.org.uk/python/mock.html"/>
	<rdf:li rdf:resource="http://ejohn.org/apps/learn/"/>
	<rdf:li rdf:resource="http://code.google.com/p/python-nose/"/>
	<rdf:li rdf:resource="http://daveastels.com/index.php?p=5"/>
	<rdf:li rdf:resource="http://peripateticaxiom.blogspot.com/2006/05/complexity-and-test-first-0.html"/>
	<rdf:li rdf:resource="http://drnicwilliams.com/2008/01/04/autotesting-javascript-in-rails/"/>
	<rdf:li rdf:resource="http://www.zenspider.com/ZSS/Products/ZenTest/"/>
	<rdf:li rdf:resource="http://blog.davidchelimsky.net/articles/2007/12/14/rspec-1-1"/>
	<rdf:li rdf:resource="http://replaced.tesugen.com/2007/10/you-cant-not-do.html"/>
	<rdf:li rdf:resource="http://rspec.rubyforge.org/"/>
	<rdf:li rdf:resource="http://blog.objectmentor.com/articles/2007/06/20/creationism-versus-natural-selection"/>
	<rdf:li rdf:resource="http://butunclebob.com/ArticleS.UncleBob.ThePrimeFactorsKata"/>
	<rdf:li rdf:resource="http://nunit.com/nunit/?p=releaseNotes&amp;r=2.4"/>
	<rdf:li rdf:resource="http://blog.daveastels.com/files/BDD_Intro.pdf"/>
	<rdf:li rdf:resource="http://behaviour-driven.org/BehaviourDrivenProgramming"/>
	<rdf:li rdf:resource="http://behaviour-driven.org/Introduction"/>
	<rdf:li rdf:resource="http://www.jrothman.com/weblog/2006/08/creating-audition-for-test-driven.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://blog.orfjackal.net/2010/04/direct-and-indirect-effects-of-tdd.html">
    <title>Random Thoughts from Esko: Direct and Indirect Effects of TDD</title>
    <dc:date>2010-04-11T12:16:57+00:00</dc:date>
    <link>http://blog.orfjackal.net/2010/04/direct-and-indirect-effects-of-tdd.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Noticing the pain as soon as possible and then fixing the problem - whether it is a rigid design, fragile tests or something else - requires skill. Not everybody is alert to the pain, but instead they keep on writing bad code until making changes becomes too expensive and a rewrite is needed. Not everybody fixes the problem when they feel the pain, but instead they implement a quick hack and leave an even bigger mess for the next developer. But for those who have the necessary skills and discipline, TDD can be a powerful tool and they can use it to write better code."
]]></description>
<dc:subject>tdd agile-practices software-development testing social-engineering good-habits</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:a137eca376df/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:good-habits"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codingdojo.org/cgi-bin/wiki.pl?KataFizzBuzz">
    <title>Coding Dojo Wiki: KataFizzBuzz</title>
    <dc:date>2010-03-19T21:10:24+00:00</dc:date>
    <link>http://codingdojo.org/cgi-bin/wiki.pl?KataFizzBuzz</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Imagine the scene. You are eleven years old, and in the five minutes before the end of the lesson, your Maths teacher decides he should make his class more "fun" by introducing a "game". He explains that he is going to point at each pupil in turn and ask them to say the next number in sequence, starting from one. The "fun" part is that if the number is divisible by three, you instead say "Fizz" and if it is divisible by five you say "Buzz". So now your maths teacher is pointing at all of your classmates in turn, and they happily shout "one!", "two!", "Fizz!", "four!", "Buzz!"... until he very deliberately points at you, fixing you with a steely gaze... time stands still, your mouth dries up, your palms become sweatier and sweatier until you finally manage to croak "Fizz!". Doom is avoided, and the pointing finger moves on. Until the next time."
]]></description>
<dc:subject>coding-dojo agility learning-by-doing self-assessment TDD BDD training kata</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f21b61c5df8f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:coding-dojo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:learning-by-doing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:self-assessment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:training"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bitcetera.com/en/techblog/2009/05/27/mac-friendly-autotest/">
    <title>Bitcetera: Mac-friendly Autotest</title>
    <dc:date>2009-05-29T11:24:58+00:00</dc:date>
    <link>http://www.bitcetera.com/en/techblog/2009/05/27/mac-friendly-autotest/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>autotest Zentest Growl programming development library ruby TDD BDD performance automation rspec Cucumber</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:e5482c18a080/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:autotest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Zentest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Growl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Cucumber"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pathf.com/blogs/2009/05/rails-testing-frequently-asked-questions-the-non-code-version/">
    <title>Agile Ajax » Rails Testing Frequently Asked Questions — The Non-Code Version » Pathfinder Development</title>
    <dc:date>2009-05-20T21:41:04+00:00</dc:date>
    <link>http://www.pathf.com/blogs/2009/05/rails-testing-frequently-asked-questions-the-non-code-version/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Things to keep in mind.

No matter where you start, start with one simple test. One assertion, if you can manage it.
Write the code to make that test pass
Then refactor -- this part is critical, this is where the creative design is with a TDD process.
Then write the next test.
In Rails, you'll often start in the controller then realize that code needs to be written in the model (or vice-versa). Write a separate test for the model -- testing models from the controller makes it hard to test all the model logic.
It's okay to plan the tests in advance, but you should only work on one test at a time. (Sometimes I'll write the series of tests, then comment out all but one)"
]]></description>
<dc:subject>test-driven-development TDD testing Rails Ruby programming-culture advice getting-hired</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:385e3ed40e2a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:getting-hired"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fakeweb.rubyforge.org/">
    <title>FakeWeb API Documentation</title>
    <dc:date>2009-04-19T23:25:22+00:00</dc:date>
    <link>http://fakeweb.rubyforge.org/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["FakeWeb is a helper for faking web requests in Ruby. It works at a global level, without modifying code or writing extensive stubs."
]]></description>
<dc:subject>Ruby programming mocks-and-stubs TDD BDD development testing</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:b2e38b7a0a3e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:mocks-and-stubs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://xunitpatterns.com/Test%20Stub.html">
    <title>Test Stub at XUnitPatterns.com</title>
    <dc:date>2009-04-15T03:05:54+00:00</dc:date>
    <link>http://xunitpatterns.com/Test%20Stub.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Variation: Saboteur
A Test Stub that is used to inject invalid indirect inputs into the SUT is often called a "Saboteur" because its purpose is to derail whatever the SUT is trying to do so we can see how the SUT copes with these circumstances. The "derailment" can be caused by returning unexpected values or objects, or it can be caused by raising an exception or causing a runtime error. Each test may either be a Simple Success Test or an Expected Exception Test (see Test Method) depending on how the SUT is expected to behave in response to the indirect input."
]]></description>
<dc:subject>testing TDD BDD rspec design-patterns programming unit-testing specification</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:5d91f36cefc5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design-patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unit-testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/btakita/rr/tree/master">
    <title>btakita's rr at master - GitHub</title>
    <dc:date>2009-04-15T02:59:18+00:00</dc:date>
    <link>http://github.com/btakita/rr/tree/master</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["RR (Double Ruby) is a test double framework that features a rich selection of double techniques and a terse syntax."
]]></description>
<dc:subject>mocks programming testing TDD BDD rspec framework ruby</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d4177fe4df36/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:mocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.claytonlz.com/index.php/2009/04/how-to-setup-rspec-cucumber-webrat-rcov-and-autotest-on-leopard/">
    <title>How To: Setup RSpec, Cucumber, Webrat, RCov and Autotest on Leopard | Clayton Lengel-Zigich</title>
    <dc:date>2009-04-10T10:52:33+00:00</dc:date>
    <link>http://www.claytonlz.com/index.php/2009/04/how-to-setup-rspec-cucumber-webrat-rcov-and-autotest-on-leopard/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["RSpec, Cucumber, Webrat, RCov and Autotest are a powerful combination of tools for testing your Rails app. Unfortunately getting them to all work nicely together can be a bit of challenge. I recently configured a development environment from scratch on OS X 10.5 Leopard and kept track of all of the little details."
]]></description>
<dc:subject>how-to rspec Rails Ruby Leopard MacOS TDD BDD autotest</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:c38bf86edf9e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:how-to"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Leopard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:MacOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:autotest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/notahat/machinist/tree/master">
    <title>notahat's machinist at master - GitHub</title>
    <dc:date>2009-03-21T14:49:25+00:00</dc:date>
    <link>http://github.com/notahat/machinist/tree/master</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Machinist generates data for the fields you don't care about, and constructs any necessary associated objects, leaving you to only specify the fields you do care about in your tests."
]]></description>
<dc:subject>BDD mocks stubs Ruby programming software-development test-driven-development library TDD factory</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8ed4546d5136/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:mocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:stubs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:factory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pathf.com/blogs/2009/03/using-cucumber-for-acceptance-testing/">
    <title>Agile Ajax » Using Cucumber for Acceptance Testing » Pathfinder Development</title>
    <dc:date>2009-03-21T14:48:40+00:00</dc:date>
    <link>http://www.pathf.com/blogs/2009/03/using-cucumber-for-acceptance-testing/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["My experience so far, as I explore what Cucumber can do, has been largely positive. Where I was starting with Cucumber and only a vague idea of how the user interaction would play out, writing the scenarios at the Cucumber level felt very valuable and gave the development a clear path that I wouldn't have otherwise had. That said, there is extra code being written, and it's clearly possible to get really tangled in getting the step definitions right."
]]></description>
<dc:subject>Cucumber BDD behavior-driven-design Ruby TDD Machinist testing agility software-development</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6cdb49f428d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Cucumber"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Machinist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nomachetejuggling.com/2009/02/21/i-love-pair-programming/">
    <title>I Love Pair-Programming » Absolutely No Machete Juggling</title>
    <dc:date>2009-02-25T01:47:39+00:00</dc:date>
    <link>http://www.nomachetejuggling.com/2009/02/21/i-love-pair-programming/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I see pairing work so well every day that I consider my career prior to my current job to have consisted mostly of wasting time. When I think back to all the code I’ve written for a job, I’m annoyed at how much less efficient I was then since I wasn’t pairing, and how much better my code and my products would have been if I had paired on them full time."
]]></description>
<dc:subject>pair-programming efficiency risk-management software development cultural-norms TDD productivity</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:a8ee056d1ff7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pair-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:efficiency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:risk-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thoughtbot.com/projects/mile_marker">
    <title>Projects - MileMarker</title>
    <dc:date>2009-02-22T00:48:14+00:00</dc:date>
    <link>http://thoughtbot.com/projects/mile_marker</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["When viewed in development mode, the person div would be overlaid with a translucent gray box with the words “Milestone 6” in it, as shown below."
]]></description>
<dc:subject>rails debugging MVC design software development TDD markup</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4824cd12ab86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:debugging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:MVC"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:markup"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://giantrobots.thoughtbot.com/2009/2/20/mixing-cucumber-with-test-unit">
    <title>Mixing Cucumber with Test::Unit/Shoulda — GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS</title>
    <dc:date>2009-02-22T00:40:33+00:00</dc:date>
    <link>http://giantrobots.thoughtbot.com/2009/2/20/mixing-cucumber-with-test-unit</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["We’ve been writing a “feature” for every new client request on that project – for each user-created ticket we handle, we create a .feature file (and include the ticket number in the feature title), and write steps for that request. This means that we have acceptance tests for all new client requests on that project. This approach may seem a little strange, but it’s been helpful, and we’re very happy with it so far. We’ll likely take a different approach if we use Cucumber on a project from scratch.

Now you have no excuse if your projects aren’t doing any kind of top-down testing, so get out there and write some acceptance tests!"
]]></description>
<dc:subject>test-driven-development TDD behavior-driven-design BDD cucumber shoulda ruby testing agility emergent-design</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1a293e6f34b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cucumber"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:shoulda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:emergent-design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thoughtbot.com/projects/shoulda">
    <title>Projects - Shoulda</title>
    <dc:date>2009-02-22T00:35:55+00:00</dc:date>
    <link>http://thoughtbot.com/projects/shoulda</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The Shoulda gem makes it easy to write elegant, understandable, and maintainable Ruby tests. Shoulda consists of test macros, assertions, and helpers added on to the Test::Unit framework. It’s fully compatible with your existing tests, and requires no retooling to use."
]]></description>
<dc:subject>TDD test-driven-development specification Ruby RoR cucumberish</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:33cff2583a7d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cucumberish"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mir.aculo.us/2006/09/16/adventures-in-javascript-testing">
    <title>mir.aculo.us</title>
    <dc:date>2009-01-09T13:32:15+00:00</dc:date>
    <link>http://mir.aculo.us/2006/09/16/adventures-in-javascript-testing</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>Javascript BDD TDD test-driven-design behavior-driven-design RoR programming presentations framework scriptaculous unittest</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:3436a117e464/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:presentations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:scriptaculous"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unittest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.objectmentor.com/articles/2008/11/27/the-truth-about-bdd">
    <title>The Truth about BDD</title>
    <dc:date>2008-12-31T15:39:12+00:00</dc:date>
    <link>http://blog.objectmentor.com/articles/2008/11/27/the-truth-about-bdd</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["But enough of irony. Is this useful? I think it may be. You see, one of the great benefits of describing a problem as a Finite State Machine (FSM) is that you can complete the logic of the problem. That is, if you can enumerate the states and the events, then you know that the number of paths through the system is no larger than S * E. Or, rather, there are no more than S*E transitions from one state to another. More importantly, enumerating them is simply a matter of creating a transition for every combination of state and event.

One of the more persistent problems in BDD (and TDD for that matter) is knowing when you are done. That is, how do you know that you have written enough scenarios (tests). Perhaps there is some condition that you have forgotten to explore, some pathway through the system that you have not described."
]]></description>
<dc:subject>via:arsyed software design BDD programming TDD behavior-driven-design analogies finite-state-machine</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:5e33503c3c92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:arsyed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:analogies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:finite-state-machine"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ericholscher.com/tag/testing-series/">
    <title>Post archive | Surfing in Kansas</title>
    <dc:date>2008-12-17T00:25:34+00:00</dc:date>
    <link>http://ericholscher.com/tag/testing-series/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>via:arsyed Python testing Django TDD (?)</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:70bd8e29a3e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:arsyed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:(?)"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rubyhoedown2008.confreaks.com/11-rick-bradley-flog-test-new.html">
    <title>Confreaks: Ruby Hoedown 2008</title>
    <dc:date>2008-11-02T13:38:23+00:00</dc:date>
    <link>http://rubyhoedown2008.confreaks.com/11-rick-bradley-flog-test-new.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[An excellent talk on testing legacy code. Some great insights on how to use judicious refactoring and contingent testing. Not too Ruby-specific.
]]></description>
<dc:subject>refactoring programming TDD BDD legacy-code software development Ruby communication</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:32439d58d8fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:refactoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:legacy-code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:communication"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.voidspace.org.uk/python/mock.html">
    <title>Mock - Mocking and Test Utilities</title>
    <dc:date>2008-10-20T14:29:38+00:00</dc:date>
    <link>http://www.voidspace.org.uk/python/mock.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>programming development library tools Python testing TDD agility</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:818b83e99f7a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ejohn.org/apps/learn/">
    <title>Learning Advanced JavaScript</title>
    <dc:date>2008-09-25T12:18:50+00:00</dc:date>
    <link>http://ejohn.org/apps/learn/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[beautiful interactive test-encompassed lessons
]]></description>
<dc:subject>javascript lesson tutorial programming web2.0 web-design TDD</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:846153c16c09/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lesson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web2.0"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/python-nose/">
    <title>python-nose - Google Code</title>
    <dc:date>2008-07-11T20:37:41+00:00</dc:date>
    <link>http://code.google.com/p/python-nose/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>unit-testing Python better programming development tes test-driven-development TDD</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:0ab7bf284fd5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unit-testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:better"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://daveastels.com/index.php?p=5">
    <title>dave astels » Why Your Code Sucks</title>
    <dc:date>2008-04-26T12:55:43+00:00</dc:date>
    <link>http://daveastels.com/index.php?p=5</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Just worth posting on the wall, is all.
]]></description>
<dc:subject>rules agility programming software development coding design testing TDD BDD</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:eed0f2ad952f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rules"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://peripateticaxiom.blogspot.com/2006/05/complexity-and-test-first-0.html">
    <title>peripatetic axiom: Complexity and Test-first 0</title>
    <dc:date>2008-02-19T01:43:16+00:00</dc:date>
    <link>http://peripateticaxiom.blogspot.com/2006/05/complexity-and-test-first-0.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>testing software development TDD agility metrics quality</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:13380bb53d3f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:quality"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drnicwilliams.com/2008/01/04/autotesting-javascript-in-rails/">
    <title>Dr Nic » Autotesting Javascript in Rails</title>
    <dc:date>2008-01-06T12:06:44+00:00</dc:date>
    <link>http://drnicwilliams.com/2008/01/04/autotesting-javascript-in-rails/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA['Below is a “getting started” tutorial, a helpful autotesting plugin, and hints about a TextMate bundle for Javascript Unit Testing and a future Peepcode on Javascript Unit Testing.'
]]></description>
<dc:subject>AJAX BDD development javascript programming Ruby TDD tutorial ZenTest</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:869cfcac0cdc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:AJAX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ZenTest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zenspider.com/ZSS/Products/ZenTest/">
    <title>ZenTest: Automated test scaffolding for Ruby</title>
    <dc:date>2007-12-24T15:22:29+00:00</dc:date>
    <link>http://www.zenspider.com/ZSS/Products/ZenTest/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>agile automation best-practices gem plugin programming Rails RoR Ruby TDD BDD unit-testing XP</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:79537d54f864/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:gem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:plugin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unit-testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.davidchelimsky.net/articles/2007/12/14/rspec-1-1">
    <title>RSpec 1.1</title>
    <dc:date>2007-12-16T14:08:34+00:00</dc:date>
    <link>http://blog.davidchelimsky.net/articles/2007/12/14/rspec-1-1</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>rspec Ruby development programming tools TDD BDD behavior-driven-development specification</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:74cd66b224ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://replaced.tesugen.com/2007/10/you-cant-not-do.html">
    <title>Tesugen Replaced: You can’t not do design</title>
    <dc:date>2007-11-22T17:50:37+00:00</dc:date>
    <link>http://replaced.tesugen.com/2007/10/you-cant-not-do.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>design philosophy emergence TDD BDD software art planning</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ea751fcc5ce6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:emergence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rspec.rubyforge.org/">
    <title>RSpec-1.0.8: Home</title>
    <dc:date>2007-11-18T19:10:43+00:00</dc:date>
    <link>http://rspec.rubyforge.org/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>extreme-programming agile BDD development documentation engineering programming Rails Ruby rubyonrails TDD testing</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d8453afe9446/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:extreme-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rubyonrails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.objectmentor.com/articles/2007/06/20/creationism-versus-natural-selection">
    <title>Creationism versus Natural Selection</title>
    <dc:date>2007-08-03T20:37:01+00:00</dc:date>
    <link>http://blog.objectmentor.com/articles/2007/06/20/creationism-versus-natural-selection</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["In the beginning, the Product Owner identified a Need. And the Need was without form, and void; and darkness was upon the face of the deep. And the Spirit of the Team (Team) moved upon the face of the Need and asked some questions."
]]></description>
<dc:subject>TDD testing software development methodologies rigor</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:dbfb0df2ae2b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:methodologies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rigor"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://butunclebob.com/ArticleS.UncleBob.ThePrimeFactorsKata">
    <title>ArticleS.UncleBob.ThePrimeFactorsKata</title>
    <dc:date>2007-04-27T20:50:10+00:00</dc:date>
    <link>http://butunclebob.com/ArticleS.UncleBob.ThePrimeFactorsKata</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Great TDD kata from UncleBob. Unfortunate it's PowerPoint; would be nice if it were a PDF. But it's legible.
]]></description>
<dc:subject>TDD test-driven-development software development design emergence agility</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:488ee821ec31/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:test-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:emergence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nunit.com/nunit/?p=releaseNotes&amp;r=2.4">
    <title>NUnit - ReleaseNotes</title>
    <dc:date>2007-03-03T14:45:49+00:00</dc:date>
    <link>http://nunit.com/nunit/?p=releaseNotes&amp;r=2.4</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[New version of NUnit testing framework is released.
]]></description>
<dc:subject>software development agile XP unit-testing TDD testing programming</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:faecbd77844d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unit-testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.daveastels.com/files/BDD_Intro.pdf">
    <title>BDD_Intro.pdf (application/pdf Object)</title>
    <dc:date>2007-03-01T02:19:43+00:00</dc:date>
    <link>http://blog.daveastels.com/files/BDD_Intro.pdf</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>BDD Ruby software development design TDD testing programming</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:bfdc9f07fe2b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://behaviour-driven.org/BehaviourDrivenProgramming">
    <title>BehaviourDrivenProgramming - Behaviour-Driven Development</title>
    <dc:date>2007-03-01T02:17:10+00:00</dc:date>
    <link>http://behaviour-driven.org/BehaviourDrivenProgramming</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["An interesting aside in favour of agile development techniques in general and TDD in particular is that even in this state the code is often much more robust and a much better functional fit than code developed under more traditional methods based on lar
]]></description>
<dc:subject>BDD TDD software development agility agile-management XP risk-management design</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ef031567927b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:risk-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://behaviour-driven.org/Introduction">
    <title>Introduction - Behaviour-Driven Development</title>
    <dc:date>2007-03-01T02:14:35+00:00</dc:date>
    <link>http://behaviour-driven.org/Introduction</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>testing behaviourdriven design software development behavior-driven-development BDD TDD</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:129f3f749b0e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behaviourdriven"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:behavior-driven-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jrothman.com/weblog/2006/08/creating-audition-for-test-driven.html">
    <title>Hiring Technical People: Creating an Audition for Test-Driven Development</title>
    <dc:date>2007-02-05T19:38:47+00:00</dc:date>
    <link>http://www.jrothman.com/weblog/2006/08/creating-audition-for-test-driven.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>hiring staffing interviewing TDD agile-management software development</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8172e6be9f40/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:staffing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:interviewing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>