<?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 (DirkSonguer)</title>
    <link>https://pinboard.in/u:DirkSonguer/public/</link>
    <description>recent bookmarks from DirkSonguer</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.businessweek.com/articles/2014-02-13/how-airbus-is-debugging-the-a350"/>
	<rdf:li rdf:resource="http://arstechnica.com/information-technology/2012/07/netflix-attacks-own-network-with-chaos-monkey-and-now-you-can-too/"/>
	<rdf:li rdf:resource="http://altdevblogaday.com/2011/08/02/some-hows-and-whys-of-usability-testing/"/>
	<rdf:li rdf:resource="http://www.alistapart.com/articles/smartphone-browser-landscape/"/>
	<rdf:li rdf:resource="https://pidoco.com/"/>
	<rdf:li rdf:resource="https://browserlab.adobe.com/"/>
	<rdf:li rdf:resource="http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/"/>
	<rdf:li rdf:resource="http://www.ibm.com/developerworks/java/library/j-ap09056/"/>
	<rdf:li rdf:resource="http://www.techradar.com/news/internet/the-ultimate-guide-to-testing-your-website-484605"/>
	<rdf:li rdf:resource="http://www.homeoftester.com/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.businessweek.com/articles/2014-02-13/how-airbus-is-debugging-the-a350">
    <title>How Airbus Is Debugging the A350 - Businessweek</title>
    <dc:date>2014-02-15T18:43:41+00:00</dc:date>
    <link>http://www.businessweek.com/articles/2014-02-13/how-airbus-is-debugging-the-a350</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Airbus (AIR:FP) must prove to itself, regulators, and its customers that the A350 works not only well but also within a hair’s breadth of perfection. What began eight years ago as a plan for Airbus’s first jet built mainly with lightweight composites is now a complex assemblage of millions of parts governed by millions of lines of computer code. The company allotted itself a year and a half to make sure it all works.]]></description>
<dc:subject>airbus testing product technology QA</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:e73a81ea7e9d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:airbus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:QA"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arstechnica.com/information-technology/2012/07/netflix-attacks-own-network-with-chaos-monkey-and-now-you-can-too/">
    <title>Netflix attacks own network with “Chaos Monkey”—and now you can too | Ars Technica</title>
    <dc:date>2012-08-01T05:48:39+00:00</dc:date>
    <link>http://arstechnica.com/information-technology/2012/07/netflix-attacks-own-network-with-chaos-monkey-and-now-you-can-too/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[By forcing Netflix engineers to recover from small failures that customers won't notice, the company hopes to prevent major outages in its video streaming service. Netflix calls the software it built to automate the process of causing failure a "Chaos Monkey," and today announced the release of Chaos Monkey's source code onto GitHub under the Apache License.]]></description>
<dc:subject>amazon cloud testing chaosmonkey tools infrastructure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:a5c2d1b6045b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:chaosmonkey"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:infrastructure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://altdevblogaday.com/2011/08/02/some-hows-and-whys-of-usability-testing/">
    <title>Some Hows and Whys of Usability Testing « #AltDevBlogADay</title>
    <dc:date>2011-08-03T11:12:23+00:00</dc:date>
    <link>http://altdevblogaday.com/2011/08/02/some-hows-and-whys-of-usability-testing/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Usability testing is on the increase led by companies like PlayableGames and Vertical Slice in the UK, and Microsoft Games Studios having offered their gameplay lab services to their exclusive developers for Xbox from before 20031. Yet it can be regarded as expensive, troublesome to organise and just a distraction from making features for a game product.

It doesn’t have to be.]]></description>
<dc:subject>usability games testing z3</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:e845ca3348aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:z3"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.alistapart.com/articles/smartphone-browser-landscape/">
    <title>A List Apart: Articles: Smartphone Browser Landscape</title>
    <dc:date>2011-01-14T22:13:06+00:00</dc:date>
    <link>http://www.alistapart.com/articles/smartphone-browser-landscape/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Users expect websites to work on their mobile phones. In two to three years, mobile support will become standard for any site. Web developers must add mobile web development to their skill set or risk losing clients.

How do you make websites mobile compatible? The answer is obvious: By testing them on all mobile phones, and by solving the problems you encounter. But, that’s a useless answer. It’s impossible to test your designs on every mobile phone out there. Within the mobile phone landscape, there are at least ten operating systems (OSs) and fifteen browsers that require consideration. Mobile devices are expensive, and not every web developer can afford to buy five to ten of them. Testing “on all mobile phones” is impossible for most web developers.

In this article, I’ll give you an overview of the mobile web market, as well as phone platforms and their browsers, so that you can decide which mobile devices to test on. Then, we’ll look at how to set up a mobile test bed.]]></description>
<dc:subject>browser mobile testing web share smartphones phones</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:afdd009b3784/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:share"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:smartphones"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:phones"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pidoco.com/">
    <title>pidoco° - wireframe creation and gui prototyping tool</title>
    <dc:date>2010-01-13T12:22:56+00:00</dc:date>
    <link>https://pidoco.com/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Schnelles Prototyping durch Drag&Drop, komplett klickbare Wireframes, Usability Testing und effiziente Kommunikation im Team - das sind die Möglichkeiten von pidoco°!
]]></description>
<dc:subject>design software tool usability testing tools wireframes prototyping ui ux gui</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:ff9a10c4113e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:tool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:wireframes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:prototyping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:gui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://browserlab.adobe.com/">
    <title>Adobe Browserlab</title>
    <dc:date>2009-06-03T12:27:55+00:00</dc:date>
    <link>https://browserlab.adobe.com/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Tool to test designs & web pages on multiple browsers automatically
]]></description>
<dc:subject>adobe tools development web design webdesign tool flash testing browser</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:1d8ff93da7e6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:adobe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:tool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:flash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:browser"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/">
    <title>Continuous Deployment at IMVU: Doing the impossible fifty times a day ...</title>
    <dc:date>2009-02-11T08:36:34+00:00</dc:date>
    <link>http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Continuous Deployment isn’t just an abstract theory. At IMVU it’s a core part of our culture to ship. It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup.
]]></description>
<dc:subject>blog programming development article agile testing deployment english</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:ce8ea1e06f64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ibm.com/developerworks/java/library/j-ap09056/">
    <title>Automation for the people: Choosing a Continuous Integration server</title>
    <dc:date>2009-02-10T13:24:13+00:00</dc:date>
    <link>http://www.ibm.com/developerworks/java/library/j-ap09056/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[With so many Continuous Integration (CI) servers to choose from, it can be difficult to decide which one is right for you. In the second article of the series Automation for the people, development automation expert Paul Duvall looks at a handful of open source CI servers, including Continuum, CruiseControl, and Luntbuild, using a consistent evaluation criteria and illustrative examples.
]]></description>
<dc:subject>development articles software testing developerworks ibm article english</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:d9edd354b939/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:articles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:developerworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:ibm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.techradar.com/news/internet/the-ultimate-guide-to-testing-your-website-484605">
    <title>The ultimate guide to testing your website</title>
    <dc:date>2008-12-01T15:46:28+00:00</dc:date>
    <link>http://www.techradar.com/news/internet/the-ultimate-guide-to-testing-your-website-484605</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[After so many shoddy sites, pop-up windows and forced registrations, the truth is that if people don't find your website easy to use, they won't come back. Worse, they'll tell their friends just how clueless you are.

The answer is, of course, to design everything around the needs of your users. We've known this for years, but there's still resistance to even the most basic usability testing.
]]></description>
<dc:subject>development web webdev articles usability testing article english</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:87c8cb7cfc8b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:articles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.homeoftester.com/">
    <title>Tester's Apple Tree</title>
    <dc:date>2008-10-29T12:37:11+00:00</dc:date>
    <link>http://www.homeoftester.com/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Nothing else, only testing!
]]></description>
<dc:subject>software development design english testing forum</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:a59f151a3167/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:forum"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>