<?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://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf"/>
	<rdf:li rdf:resource="http://www.inc.com/magazine/20110201/how-to-turn-disaster-into-gold.html"/>
	<rdf:li rdf:resource="http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf">
    <title>How Complex Systems Fail</title>
    <dc:date>2015-09-07T16:44:54+00:00</dc:date>
    <link>http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Being a Short Treatise on the Nature of Failure; How Failure is Evaluated; How Failure is Attributed to Proximate Cause; and the Resulting New Understanding of Patient Safety]]></description>
<dc:subject>failure systems complexity</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:40b870adaf51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:complexity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.inc.com/magazine/20110201/how-to-turn-disaster-into-gold.html">
    <title>How to Turn Disaster Into Gold</title>
    <dc:date>2011-05-30T14:56:16+00:00</dc:date>
    <link>http://www.inc.com/magazine/20110201/how-to-turn-disaster-into-gold.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[We're very careful about how we explain downtime and other glitches. We don't beat around the bush. We don't try to hedge. We don't pass the blame to a vendor or another party. When our customers are affected, it's on us.]]></description>
<dc:subject>failure customer-service</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:25654ac000e5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:customer-service"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html">
    <title>Coding Horror: Working with the Chaos Monkey</title>
    <dc:date>2011-05-30T14:02:17+00:00</dc:date>
    <link>http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[One of the first systems our engineers built in AWS is called the Chaos Monkey. The Chaos Monkey’s job is to randomly kill instances and services within our architecture. If we aren’t constantly testing our ability to succeed despite failure, then it isn’t likely to work when it matters most – in the event of an unexpected outage.

]]></description>
<dc:subject>programming failure performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:8c580aa05b0d/</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:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>