<?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://writing.kemitchell.com/2022/01/06/Name-Functional-Specs.html"/>
	<rdf:li rdf:resource="https://www.synology.com/en-us/support/RAID_calculator"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1507.06988"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1105.0322"/>
	<rdf:li rdf:resource="http://dret.typepad.com/dretblog/html5-api-overview.html"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1106.1796"/>
	<rdf:li rdf:resource="http://dana.org/news/cerebrum/detail.aspx?id=32066"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1006.4892"/>
	<rdf:li rdf:resource="http://www.ietf.org/rfc/rfc2445.txt"/>
	<rdf:li rdf:resource="http://www.whatwg.org/specs/web-workers/current-work/"/>
	<rdf:li rdf:resource="http://www.loc.gov/cds/FRBR.html"/>
	<rdf:li rdf:resource="http://xunitpatterns.com/Test%20Stub.html"/>
	<rdf:li rdf:resource="http://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/"/>
	<rdf:li rdf:resource="http://thoughtbot.com/projects/shoulda"/>
	<rdf:li rdf:resource="http://www.khronos.org/news/press/releases/the_khronos_group_releases_opencl_1.0_specification/"/>
	<rdf:li rdf:resource="http://blog.davidchelimsky.net/articles/2007/12/14/rspec-1-1"/>
	<rdf:li rdf:resource="http://blog.davidchelimsky.net/articles/2007/11/29/nested-example-groups"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/PDF/A"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://writing.kemitchell.com/2022/01/06/Name-Functional-Specs.html">
    <title>What Do We Call Functional Specs for Legal Forms? — /dev/lawyer</title>
    <dc:date>2022-05-22T12:07:35+00:00</dc:date>
    <link>https://writing.kemitchell.com/2022/01/06/Name-Functional-Specs.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Paired with a database of sections that actually implement each kind of component, we could use these lists like recipes. A computer could give users their pick of specific language options for each component, like a grocery store offering different brands and flavors for each ingredient. In pulling together an NDA, you might choose a definition of “Confidential Information” that does or does not require marking and written confirmation. You might choose a return-and-destruction component that does or doesn’t require certification of destruction after the agreement ends.
I think these kinds of lists could be an especially amenable to online collaboration, since they’re both conceptually straightforward and easy to type. Fundamentally, they’re just text files with a title at the top and a list of components after. The only tricky part would be making sure that lines in the lists correspond to labels in the database of drafted sections, if the two are going to work together.
]]></description>
<dc:subject>law contracts rather-interesting specification consider:testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6452770b59cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:contracts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rather-interesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:consider:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.synology.com/en-us/support/RAID_calculator">
    <title>RAID Calculator | Synology Inc.</title>
    <dc:date>2017-10-14T23:12:41+00:00</dc:date>
    <link>https://www.synology.com/en-us/support/RAID_calculator</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>NAS hardware specification configurator to-understand</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:01b4dfdd15b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:NAS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:configurator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:to-understand"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1507.06988">
    <title>[1507.06988] A Binary Data Stream Scripting Language</title>
    <dc:date>2015-09-14T11:16:23+00:00</dc:date>
    <link>http://arxiv.org/abs/1507.06988</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Any file is fundamentally a binary data stream. A practical solution was achieved to interpret binary data stream. A new scripting language named Data Format Scripting Language (DFSL) was developed to describe the physical layout of the data in a structural, more intelligible way. On the basis of the solution, a generic software application was implemented; it parses various binary data streams according to their respective DFSL scripts and generates human-readable result and XML document for data sharing. Our solution helps eliminate the error-prone low-level programming, especially in the hardware devices or network protocol development/debugging processes.
]]></description>
<dc:subject>rather-interesting computer-science programming-language data-analysis specification domain-specific-languages parsing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ca286c56e8be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rather-interesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:computer-science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming-language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:data-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:domain-specific-languages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:parsing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1105.0322">
    <title>[1105.0322] A Computational Model for the Direct Execution of General Specifications with Multi-way Constraints</title>
    <dc:date>2013-02-25T12:16:04+00:00</dc:date>
    <link>http://arxiv.org/abs/1105.0322</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[In this paper, we propose a computational model for the direct execution of general specifications with multi-way constraints. Although this computational model has a similar structure to existing constraint programming models, it is not meant for solving constraint satisfaction problems but rather for the simulation of social systems and to continue to execute assigned processes. Because of this similar structure, it is applicable to the spectrum of the constraint solver, which is purple in this model. Essentially, it is a technology that can speed up the construction of large-scale network systems. This model can be efficiently executed to directly describe design content in a simple way.]]></description>
<dc:subject>constraint-programming programming-language specification design architecture nudge-targets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6436dfd66bbe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:constraint-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming-language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:nudge-targets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dret.typepad.com/dretblog/html5-api-overview.html">
    <title>HTML5 Landscape Overview - dretblog</title>
    <dc:date>2012-08-20T14:49:07+00:00</dc:date>
    <link>http://dret.typepad.com/dretblog/html5-api-overview.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["here is a list of the functionality and APIs currently under development as standalone documents in the W3C (links are to the latest version, order is alphabetical by title, the list contains 49 specs):"]]></description>
<dc:subject>HTML html5 specification quite-a-backlog that-word-standard-you-keep-using-it</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:dfcadcd29d4a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:quite-a-backlog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:that-word-standard-you-keep-using-it"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1106.1796">
    <title>[1106.1796] Accelerating Reinforcement Learning by Composing Solutions of Automatically Identified Subtasks</title>
    <dc:date>2011-10-04T11:48:29+00:00</dc:date>
    <link>http://arxiv.org/abs/1106.1796</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["This paper discusses a system that accelerates reinforcement learning by using transfer from related tasks. Without such transfer, even if two tasks are very similar at some abstract level, an extensive re-learning effort is required. The system achieves much of its power by transferring parts of previously learned solutions rather than a single complete solution. The system exploits strong features in the multi-dimensional function produced by reinforcement learning in solving a particular task. These features are stable and easy to recognize early in the learning process. They generate a partitioning of the state space and thus the function. The partition is represented as a graph. This is used to index and compose functions stored in a case base to form a close approximation to the solution of the new task. Experiments demonstrate that function composition often produces more than an order of magnitude increase in learning rate compared to a basic reinforcement learning algorithm."]]></description>
<dc:subject>algorithms learning problem-solving decomposition specification nudge-targets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:b07ed43ea2b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:problem-solving"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:decomposition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:nudge-targets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dana.org/news/cerebrum/detail.aspx?id=32066">
    <title>Diagnosing the DSM - Dana Foundation</title>
    <dc:date>2011-05-15T13:08:36+00:00</dc:date>
    <link>http://dana.org/news/cerebrum/detail.aspx?id=32066</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[With respect to the DSM-5, I am agnostic about the diagnostic criteria for individual conditions, such as panic disorder or generalized anxiety disorder; in the end, I am not certain that either of these categories capture nature or will even appear in the DSM-6. When it comes to individual diagnostic categories, I would recommend that the DSM-5 take a conservative approach, leaving criteria unchanged unless compelling new evidence suggests that a change would be beneficial. Whatever the ultimate approach to the DSM-5, it is critical that the scientific community escape the artificial diagnostic silos that control so much research, ultimately to our detriment.

]]></description>
<dc:subject>medical-culture diagnosis specification over-specification standard-setting-play pragmatism-it-ain't</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:a55ba73ff8bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:medical-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:diagnosis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:over-specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:standard-setting-play"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pragmatism-it-ain't"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1006.4892">
    <title>[1006.4892] Mapping Business Process Modeling constructs to Behavior Driven Development Ubiquitous Language</title>
    <dc:date>2010-07-29T14:45:02+00:00</dc:date>
    <link>http://arxiv.org/abs/1006.4892</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Behavior-Driven Development (BDD) is a specification technique that automatically certifies that all functional requirements are treated properly by source code, through the connection of the textual description of these requirements to automated tests. Given that in some areas, in special Enterprise Information Systems, requirements are identified by Business Process Modeling - which uses graphical notations of the underlying business processes, this paper aims to provide a mapping from the basic constructs that form the most common BPM languages to Behavior Driven Development constructs."
]]></description>
<dc:subject>models BDD software-development-is-not-programming specification uml maybe-not-so-much-satire</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:7e61f2333d56/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<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:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:uml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:maybe-not-so-much-satire"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ietf.org/rfc/rfc2445.txt">
    <title>http://www.ietf.org/rfc/rfc2445.txt</title>
    <dc:date>2009-12-16T12:34:13+00:00</dc:date>
    <link>http://www.ietf.org/rfc/rfc2445.txt</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["   This memo defines the format for specifying iCalendar object methods.
   An iCalendar object method is a set of usage constraints for the
   iCalendar object. For example, these methods might define scheduling
   messages that request an event be scheduled, reply to an event
   request, send a cancellation notice for an event, modify or replace
   the definition of an event, provide a counter proposal for an
   original event request, delegate an event request to another
   individual, request free or busy time, reply to a free or busy time
   request, or provide similar scheduling messages for a to-do or
   journal entry calendar component. The iCalendar Transport-indendent
   Interoperability Protocol (iTIP) defined in [ITIP] is one such
   scheduling protocol."
]]></description>
<dc:subject>iCal RFP programming reference standards documentation API specification projects spec</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8329305b2d40/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:iCal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RFP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:API"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:projects"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:spec"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.whatwg.org/specs/web-workers/current-work/">
    <title>Web Workers</title>
    <dc:date>2009-10-30T21:49:16+00:00</dc:date>
    <link>http://www.whatwg.org/specs/web-workers/current-work/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism."
]]></description>
<dc:subject>web-applications standard-setting-play distributed-processing programming standards API specification HTML5 threads Nudge</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4228fef208b3/</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:standard-setting-play"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:API"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:HTML5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:threads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Nudge"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/cds/FRBR.html">
    <title>What is FRBR?</title>
    <dc:date>2009-04-21T11:15:42+00:00</dc:date>
    <link>http://www.loc.gov/cds/FRBR.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Based on an article originally published in Technicalities (v. 25, no. 5, Sept./Oct. 2003), this pamphlet provides a brief overview of the Functional Requirements for Bibliographic Records (FRBR) as developed by the International Federation of Library Associations (IFLA). Using full-color graphics, What is FRBR? outlines the background of the development of the Functional Requirements, the concepts involved and their potential impact on cataloging rules, bibliographic structures and systems design for cataloging applications."
]]></description>
<dc:subject>books cataloging bibliography metadata libraries technical specification ontology bookphile bibliographies</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:e41cb0e8fdc9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:technical"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:bookphile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:bibliographies"/>
</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://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/">
    <title>My Least Favorite Interview Question » Absolutely No Machete Juggling</title>
    <dc:date>2009-02-24T23:08:35+00:00</dc:date>
    <link>http://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I have no idea what the interviewer’s expectations are, so I have to guess. I have, essentially, a 50/50 shot at guessing correctly. To make matters worse, my answer will likely go through a number of different interviewers, and I have a 50/50 shot at having guessed correctly with each of them. Assuming that a single “no” from one of the interviewers means I don’t get a job offer, having 2 interviewers gives me a 25% chance of success. Three interviewers gives me a 12.5% chance. A team of 6 or 7 interviewers (extremely common in up-and-coming companies) gives me virtually no chance at all."
]]></description>
<dc:subject>Nudge programming interview hiring specification assumptions project-management business-culture</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2962542e9d13/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Nudge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:interview"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
</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://www.khronos.org/news/press/releases/the_khronos_group_releases_opencl_1.0_specification/">
    <title>Khronos Press Releases - The Khronos Group Releases OpenCL 1.0 Specification</title>
    <dc:date>2008-12-12T12:18:27+00:00</dc:date>
    <link>http://www.khronos.org/news/press/releases/the_khronos_group_releases_opencl_1.0_specification/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["“The opportunity to effectively unlock the capabilities of new generations of programmable compute and graphics processors drove the unprecedented level of cooperation to refine the initial proposal from Apple into the ratified OpenCL 1.0 specification,” said Neil Trevett, chair of the OpenCL working group, president of the Khronos Group and vice president at NVIDIA. “As an open, cross-platform standard, OpenCL is a fundamental technology for next generation software development that will play a central role in the Khronos API ecosystem and we look forward to seeing implementations within the next year.”
]]></description>
<dc:subject>OpenCL via:logista GPU specification programming Snow-Leopard computation Nudge</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:36cd5f7560d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:OpenCL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:logista"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GPU"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Snow-Leopard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:computation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Nudge"/>
</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://blog.davidchelimsky.net/articles/2007/11/29/nested-example-groups">
    <title>Nested Example Groups</title>
    <dc:date>2007-12-02T16:17:13+00:00</dc:date>
    <link>http://blog.davidchelimsky.net/articles/2007/11/29/nested-example-groups</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Love the example
]]></description>
<dc:subject>rspec Ruby RoR Rails BDD behavior-driven-development specification agility agile-management requirements programming</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4274b8e15e1a/</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:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<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: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:requirements"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/PDF/A">
    <title>PDF/A - Wikipedia, the free encyclopedia</title>
    <dc:date>2007-12-02T13:26:21+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/PDF/A</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Wondering about type designers' license agreements.
]]></description>
<dc:subject>formats specification archive presentation preservation PDF PDF/A library digitization publishing standards</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:94ea304327b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:formats"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:presentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:preservation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:PDF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:PDF/A"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:digitization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>