<?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="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0188299"/>
	<rdf:li rdf:resource="https://blog.plan99.net/building-account-systems-f790bf5fdbe0"/>
	<rdf:li rdf:resource="http://n-gate.com/software/2017/07/12/0/"/>
	<rdf:li rdf:resource="http://daniellakens.blogspot.co.uk/2017/04/five-reasons-blog-posts-are-of-higher.html"/>
	<rdf:li rdf:resource="https://robertovitillo.com/2015/06/30/spark-best-practices/"/>
	<rdf:li rdf:resource="http://engineering.appfolio.com/2012/11/16/css-architecture/"/>
	<rdf:li rdf:resource="http://veltman.tumblr.com/post/44638298912/how-to-not-screw-up-your-data"/>
	<rdf:li rdf:resource="http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html"/>
	<rdf:li rdf:resource="http://arkitus.com/PRML/"/>
	<rdf:li rdf:resource="https://smacss.com/"/>
	<rdf:li rdf:resource="http://www.smashingmagazine.com/2008/09/16/jquery-examples-and-best-practices/"/>
	<rdf:li rdf:resource="http://www.kalzumeus.com/2010/12/12/staging-servers-source-control-deploy-workflows-and-other-stuff-nobody-teaches-you/"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1008.0941"/>
	<rdf:li rdf:resource="http://lizkeogh.com/2010/07/23/what-not-to-test/"/>
	<rdf:li rdf:resource="http://testobsessed.com/wordpress/wp-content/uploads/2007/02/testheuristicscheatsheetv1.pdf"/>
	<rdf:li rdf:resource="http://www.w3.org/2001/tag/awwsw/http-goes-bad-20100602.html"/>
	<rdf:li rdf:resource="http://eggsonbread.com/2010/03/28/my-rspec-best-practices-and-tips/"/>
	<rdf:li rdf:resource="http://japhr.blogspot.com/2010/03/watching-for-keeps.html"/>
	<rdf:li rdf:resource="http://wonderfullyflawed.com/2009/07/02/get-your-api-right/"/>
	<rdf:li rdf:resource="http://blog.rubybestpractices.com/posts/gregory/020-rbp-ch6.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+RubyBestPractices+(Ruby+Best+Practices+-+Blog)"/>
	<rdf:li rdf:resource="http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices"/>
	<rdf:li rdf:resource="http://www.zeldman.com/2009/05/12/customer-service-not-ruby-on-rails/"/>
	<rdf:li rdf:resource="http://www.roadfood.com/Reviews/Overview.aspx?RefID=3612"/>
	<rdf:li rdf:resource="http://www.zenspider.com/ZSS/Products/ZenTest/"/>
	<rdf:li rdf:resource="http://www.macresearch.org/macintosh_management_best_practices_tips_and_tricks"/>
	<rdf:li rdf:resource="http://www.manageability.org/blog/stuff/google-development-practice-lean-production"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0188299">
    <title>Second-generation p-values: Improved rigor, reproducibility, &amp; transparency in statistical analyses</title>
    <dc:date>2019-03-29T12:53:38+00:00</dc:date>
    <link>https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0188299</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Verifying that a statistically significant result is scientifically meaningful is not only good scientific practice, it is a natural way to control the Type I error rate. Here we introduce a novel extension of the p-value—a second-generation p-value (pδ)–that formally accounts for scientific relevance and leverages this natural Type I Error control. The approach relies on a pre-specified interval null hypothesis that represents the collection of effect sizes that are scientifically uninteresting or are practically null. The second-generation p-value is the proportion of data-supported hypotheses that are also null hypotheses. As such, second-generation p-values indicate when the data are compatible with null hypotheses (pδ = 1), or with alternative hypotheses (pδ = 0), or when the data are inconclusive (0 < pδ < 1). Moreover, second-generation p-values provide a proper scientific adjustment for multiple comparisons and reduce false discovery rates. This is an advance for environments rich in data, where traditional p-value adjustments are needlessly punitive. Second-generation p-values promote transparency, rigor and reproducibility of scientific results by a priori specifying which candidate hypotheses are practically meaningful and by providing a more reliable statistical summary of when the data are compatible with alternative or null hypotheses.

]]></description>
<dc:subject>statistics experimental-design philosophy-of-science define-your-terms performance-measure rather-interesting to-watch prescriptive-advice best-practices academic-culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4bf3aaf00953/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:experimental-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:philosophy-of-science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:define-your-terms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:performance-measure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rather-interesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-watch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:prescriptive-advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:academic-culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.plan99.net/building-account-systems-f790bf5fdbe0">
    <title>Building account systems – Mike’s blog</title>
    <dc:date>2017-08-05T11:28:05+00:00</dc:date>
    <link>https://blog.plan99.net/building-account-systems-f790bf5fdbe0</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Troy Hunt recently published a blog post titled “Authentication guidance for the modern era”. It has a big pile of solid advice on what password rules your website should use, with references to formal government recommendations — always useful for convincing colleagues or a boss.
One of the projects I worked on during my time at Google was their unified account system (specifically, anti-hijacking). Login systems are a part of most websites, so reading Troy’s article inspired me to put together some advice for building them.]]></description>
<dc:subject>software-development-is-not-programming best-practices authentication to-read to-learn security reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:b7f227abcf11/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development-is-not-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:authentication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-read"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-learn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://n-gate.com/software/2017/07/12/0/">
    <title>n-gate.com. we can't both be right.</title>
    <dc:date>2017-07-21T13:08:54+00:00</dc:date>
    <link>http://n-gate.com/software/2017/07/12/0/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[An internet lectures passersby about webshit. The lectures are sprinkled with advertisements for an HTTP server that runs as root. We are expected to take security advice from this person seriously.

We do not.]]></description>
<dc:subject>web-applications to-do best-practices devops le-sigh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:41d60e3ab08c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-do"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:le-sigh"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://daniellakens.blogspot.co.uk/2017/04/five-reasons-blog-posts-are-of-higher.html">
    <title>The 20% Statistician: Five reasons blog posts are of higher scientific quality than journal articles</title>
    <dc:date>2017-05-07T14:29:04+00:00</dc:date>
    <link>http://daniellakens.blogspot.co.uk/2017/04/five-reasons-blog-posts-are-of-higher.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Five reasons blog posts are of higher scientific quality than journal articles
]]></description>
<dc:subject>academia academic-culture publishing philosophy-of-science citation best-practices to-write-about</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f4bc4c6f0b5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:academic-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:philosophy-of-science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:citation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-write-about"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://robertovitillo.com/2015/06/30/spark-best-practices/">
    <title>Spark best practices | Roberto Agostino Vitillo's Blog</title>
    <dc:date>2017-04-13T11:06:58+00:00</dc:date>
    <link>https://robertovitillo.com/2015/06/30/spark-best-practices/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[We have been running Spark for a while now at Mozilla and this post is a summary of things we have learned about tuning and debugging Spark jobs.

]]></description>
<dc:subject>via:arthegall Spark best-practices data-structures performance-measure distributed-processing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f8f1e78b5901/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:arthegall"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Spark"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:data-structures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:performance-measure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-processing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.appfolio.com/2012/11/16/css-architecture/">
    <title>CSS Architecture | Appfolio Engineering</title>
    <dc:date>2013-05-11T23:04:09+00:00</dc:date>
    <link>http://engineering.appfolio.com/2012/11/16/css-architecture/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[The best way to make sure your selectors don’t style unwanted elements is to not give them the opportunity. A selector like #main-nav ul li ul li div could very easily end up applying to unwanted elements as your markup changes down the road. A style like .subnav, on the other hand, will have absolutely no chance of accidentally applying to an unwanted element. Applying classes directly to the elements you want to style is the best way to keep your CSS predictable.

]]></description>
<dc:subject>css web-design graphic-design best-practices advice</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ba8cc8543062/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:graphic-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://veltman.tumblr.com/post/44638298912/how-to-not-screw-up-your-data">
    <title>Noah Veltman - How To Not Screw Up Your Data</title>
    <dc:date>2013-03-07T11:31:22+00:00</dc:date>
    <link>http://veltman.tumblr.com/post/44638298912/how-to-not-screw-up-your-data</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[and why aren't these Cucumber tests?]]></description>
<dc:subject>data-analysis best-practices the-mangle-in-practice GIGO the-part-that-machines-can't-learn</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8744b79fbad9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:data-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:the-mangle-in-practice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GIGO"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:the-part-that-machines-can't-learn"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html">
    <title>Please stop embedding Bootstrap classes in your HTML!</title>
    <dc:date>2012-11-01T21:31:08+00:00</dc:date>
    <link>http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["What's wrong with this? First of all, by embedding appearance-oriented code into our HTML, we're bucking the evolutionary trend of web development of the last 10 years. Jeffrey Zeldman's seminal 2003 work "Designing with Web Standards" explains the benefits of keeping code in separate layers for content, presentation and behavior: by structuring HTML around what content means, rather than how it looks, you can later change the way it looks without having to edit both the HTML and the CSS."]]></description>
<dc:subject>twitter-bootstrap css web-design best-practices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:7340888f7ffd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:twitter-bootstrap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arkitus.com/PRML/">
    <title>Patterns for Research in Machine Learning (S. M. Ali Eslami)</title>
    <dc:date>2012-08-16T21:45:52+00:00</dc:date>
    <link>http://arkitus.com/PRML/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[to be stolen and propagated in The Book]]></description>
<dc:subject>machine-learning data-analysis best-practices via:arsyed</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:dd2574519e05/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:machine-learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:data-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:arsyed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://smacss.com/">
    <title>Home - Scalable and Modular Architecture for CSS</title>
    <dc:date>2012-04-21T13:06:53+00:00</dc:date>
    <link>https://smacss.com/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I’ve been analyzing my process (and the process of those around me) and figuring out how best to structure code for projects on a larger scale. What I've found is a process that works equally well for sites small and large.

Learn how to structure your CSS to allow for flexibility and maintainability as your project and your team grows."]]></description>
<dc:subject>css tutorial best-practices graphic-design via-trek</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:50d9eb330a7b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:graphic-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via-trek"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.smashingmagazine.com/2008/09/16/jquery-examples-and-best-practices/">
    <title>jQuery and JavaScript Coding: Examples and Best Practices - Smashing Magazine</title>
    <dc:date>2011-05-09T10:20:20+00:00</dc:date>
    <link>http://www.smashingmagazine.com/2008/09/16/jquery-examples-and-best-practices/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["While the term “DOM scripting” really just refers to the use of scripts (in this case, Javascripts) to access the Document Object Model, it has widely become accepted as a way of describing what should really be called “unobtrusive DOM scripting”—basically, the art of adding Javascript to your page in such a way that if there were NO Javascript, the page would still work (or at least degrade gracefully). In the website world, our DOM scripting is done using Javascript."]]></description>
<dc:subject>javascript DOM-scripting unobtrusive-javacript best-practices tutorial web-applications</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4b839ec178b4/</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:DOM-scripting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:unobtrusive-javacript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-applications"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.kalzumeus.com/2010/12/12/staging-servers-source-control-deploy-workflows-and-other-stuff-nobody-teaches-you/">
    <title>Staging Servers, Source Control &amp; Deploy Workflows, And Other Stuff Nobody Teaches You: MicroISV on a Shoestring</title>
    <dc:date>2010-12-13T23:54:07+00:00</dc:date>
    <link>http://www.kalzumeus.com/2010/12/12/staging-servers-source-control-deploy-workflows-and-other-stuff-nobody-teaches-you/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["You already have geniuses working on your infrastructure.  Listen to them.  This article is for people who don’t have any option between “code runs on developer’s laptop” and “code runs in production.”"
]]></description>
<dc:subject>software-development best-practices best-laid-plans</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:db3ebab5c532/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-laid-plans"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1008.0941">
    <title>[1008.0941] Timing matters: Lessons From The CA Literature On Updating</title>
    <dc:date>2010-08-12T19:32:46+00:00</dc:date>
    <link>http://arxiv.org/abs/1008.0941</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["In the present article we emphasize the importance of modeling time in the context of agent-based models. To this end, we present a (selective) survey of the Cellular Automata-literature on updating and draw parallels to the issue of agent activation in agent-based models. By means of two simple models, Schelling's segregation model and Epstein's demographic prisoner's dilemma we investigate the influence of choosing different regimes of agent activation. Our experiments indicate that timing is not a critical issue for very simple models but bears huge influence on model behavior and results as soon as the degree of complexity increases only so slightly. After a brief review of the way commonly used ABM simulation environments handle the issue of timing, we draw some tentative conclusions about the importance of timing and the need for more research towards that direction, similar to the concerted effort on updating in cellular automata."
]]></description>
<dc:subject>cellular-automata complexology best-practices assumptions agent-based bias nudge-targets?</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:a2a2c8ef5df9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cellular-automata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:complexology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agent-based"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:bias"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:nudge-targets?"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lizkeogh.com/2010/07/23/what-not-to-test/">
    <title>Liz Keogh's blog » What not to test</title>
    <dc:date>2010-08-12T12:27:56+00:00</dc:date>
    <link>http://lizkeogh.com/2010/07/23/what-not-to-test/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Work out which bits of the system you know least about. Create the scenarios and have conversations around those bits of the system. You don’t have to grow the system from the beginning – you can pick any point you like! Which bits of the system make you most uncomfortable? Which bits make your stakeholders most uncomfortable?"
]]></description>
<dc:subject>agility bdd behavior-driven-design best-practices advice software-development</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:62088bf41f2d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<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:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://testobsessed.com/wordpress/wp-content/uploads/2007/02/testheuristicscheatsheetv1.pdf">
    <title>TEST HEURISTICS CHEAT SHEET [pdf]</title>
    <dc:date>2010-06-05T21:10:55+00:00</dc:date>
    <link>http://testobsessed.com/wordpress/wp-content/uploads/2007/02/testheuristicscheatsheetv1.pdf</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>agile-practices testing software-development hints agility best-practices</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:64c2e4906aed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/2001/tag/awwsw/http-goes-bad-20100602.html">
    <title>When HTTP Goes Bad</title>
    <dc:date>2010-06-04T10:37:13+00:00</dc:date>
    <link>http://www.w3.org/2001/tag/awwsw/http-goes-bad-20100602.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["This memo considers three radical ideas applying to the Web, not necessarily as serious proposals (although given support they could be turned into such) but as thought experiments or fantasies meant to sharpen the discussion of the "meaning" of URIs and other current issues of web architecture. The first fantasy is the idea that a URI's meaning is in how it is used, not what it "identifies". The second is the prospect of second sourcing for URI behavior. The third is the idea of encyclopedia-style documentation for URIs."
]]></description>
<dc:subject>semantic-web commons social-norms resources best-practices property thought-experiments via:arthegall</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:575317730cf3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:semantic-web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:commons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:property"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:thought-experiments"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:arthegall"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://eggsonbread.com/2010/03/28/my-rspec-best-practices-and-tips/">
    <title>(My) RSpec best practices and tips | EggsOnBread</title>
    <dc:date>2010-03-31T23:06:06+00:00</dc:date>
    <link>http://eggsonbread.com/2010/03/28/my-rspec-best-practices-and-tips/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["After a year using RSpec, I’m happy to share “(My) RSpec Best Practices and Tips”. Let’s make your specs easier to maintain, less verbose, more structured and covering more cases!"
]]></description>
<dc:subject>rspec Ruby programming BDD behavior-driven-design best-practices tips testing</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6b3f45516e67/</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:programming"/>
	<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:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://japhr.blogspot.com/2010/03/watching-for-keeps.html">
    <title>japh(r): Watching, For Keeps</title>
    <dc:date>2010-03-12T15:24:54+00:00</dc:date>
    <link>http://japhr.blogspot.com/2010/03/watching-for-keeps.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I am fairly obsessive about deleting prototype code. The code that I produced might be fine, it might not. It is more than likely that it is not great because I was learning something new and making mistakes along the way. I do not want to be in a position to be building on crap code. I alway build on the simplest thing that can possibly work. The only way to be sure of that (that I know of) is BDD."
]]></description>
<dc:subject>software-development kill-your-favorites best-practices BDD walkthrough</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:5c69f5a80fa0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kill-your-favorites"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:walkthrough"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wonderfullyflawed.com/2009/07/02/get-your-api-right/">
    <title>Get Your API Right « Trek</title>
    <dc:date>2010-03-10T15:31:56+00:00</dc:date>
    <link>http://wonderfullyflawed.com/2009/07/02/get-your-api-right/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Every project I’ve worked on in the last two years has heavily involved the use of web APIs. Libersy at the time (no idea about now) had an architecture that was extensively API based, even for communication between internal applications (an architecture I strongly argued against, bee tea dubs). Since then I’ve futzed with web APIs almost exclusively. From very narrow focused uses like University of Michigan’s Bluestream Service, to more broad but still fairly local APIs like the Ann Arbor District Library’s soon-to-be-updated API, all the way to APIs of major web applications like Twitter and Flickr.

Constant exposure has turned me into a bit of a snob: I can’t stand working with a poorly designed API! If you’re about to design or release an API for the web and want to avoid the ire of your developers, I’ve summed up the best (and worst) of what I’ve seen into 8 rules:"
]]></description>
<dc:subject>API software-development interoperability architecture design best-practices</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:60a94cdb4ef7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:API"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:interoperability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.rubybestpractices.com/posts/gregory/020-rbp-ch6.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+RubyBestPractices+(Ruby+Best+Practices+-+Blog)">
    <title>Ruby Best Practices - Ruby Tuesdays: RBP Chapter 6</title>
    <dc:date>2010-03-07T22:14:59+00:00</dc:date>
    <link>http://blog.rubybestpractices.com/posts/gregory/020-rbp-ch6.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+RubyBestPractices+(Ruby+Best+Practices+-+Blog)</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Readers are encouraged to fight RBP as they read it, rather than just soaking up the information. Although I claim this book is about “Best Practices”, the only reason that is true is that it’s a result of countless conversations with folks who are deep in the Ruby trenches getting stuff done. The only way for RBP to remain current and relevant is to continue these discussions, using its content as a jumping off point for fresh ideas."
]]></description>
<dc:subject>open-access software-development ruby best-practices programming O'Reilly conversation-trumps-lecturing</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d13e7d8739fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-access"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:O'Reilly"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:conversation-trumps-lecturing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices">
    <title>Riding Rails: Gem Packaging: Best Practices</title>
    <dc:date>2009-09-03T11:06:40+00:00</dc:date>
    <link>http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["When you call load or require a new file, Ruby searches through the files in its load path. This allows you to require files relative to the load path without specifying the files full system path."
]]></description>
<dc:subject>programming Ruby tutorial tips best-practices</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2c42ddc40007/</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:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zeldman.com/2009/05/12/customer-service-not-ruby-on-rails/">
    <title>Jeffrey Zeldman Presents : Customer service, not Ruby on Rails</title>
    <dc:date>2009-05-19T13:00:36+00:00</dc:date>
    <link>http://www.zeldman.com/2009/05/12/customer-service-not-ruby-on-rails/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["37signals not only constantly fine-tunes their products, they also think about the customer experience even when the customer is leaving.

I find that instructive, educational, and inspiring."
]]></description>
<dc:subject>customer-service business-culture web-design courtesy design user-experience best-practices</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:be51848b94c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:customer-service"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:courtesy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:user-experience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.roadfood.com/Reviews/Overview.aspx?RefID=3612">
    <title>Owl Bar - San Antonio, NM</title>
    <dc:date>2008-09-12T20:21:21+00:00</dc:date>
    <link>http://www.roadfood.com/Reviews/Overview.aspx?RefID=3612</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Ed, who's ever heard of that place?? The OWL in San Antonio NM has the best green chile cheeseburger in the WORLD.

Period.
]]></description>
<dc:subject>food New-Mexico green-chile-cheeseburgers smackdown reviews food-food foodie localism best-practices recipes</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:68083dc6b9ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:food"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:New-Mexico"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:green-chile-cheeseburgers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:smackdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:reviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:food-food"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:foodie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:localism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:recipes"/>
</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://www.macresearch.org/macintosh_management_best_practices_tips_and_tricks">
    <title>Macintosh Management: Best Practices, Tips and Tricks - MacResearch</title>
    <dc:date>2007-07-08T20:02:33+00:00</dc:date>
    <link>http://www.macresearch.org/macintosh_management_best_practices_tips_and_tricks</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>MacOS system-administration research administration best-practices advice IT</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:95c057fe47e3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:MacOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:system-administration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:administration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:IT"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.manageability.org/blog/stuff/google-development-practice-lean-production">
    <title>The Lean Nature of Google's Development Practices .: Manageability :.</title>
    <dc:date>2007-01-28T12:28:47+00:00</dc:date>
    <link>http://www.manageability.org/blog/stuff/google-development-practice-lean-production</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>agility lean development Google methodologies management business best-practices</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:71861a85989c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:methodologies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:best-practices"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>