<?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 (michielbuddingh)</title>
    <link>https://pinboard.in/u:michielbuddingh/public/</link>
    <description>recent bookmarks from michielbuddingh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://github.com/google/git-appraise"/>
	<rdf:li rdf:resource="https://danluu.com/wat/"/>
	<rdf:li rdf:resource="http://aspiringcraftsman.com/2007/08/25/interactive-application-architecture/"/>
	<rdf:li rdf:resource="http://google-engtools.blogspot.com/"/>
	<rdf:li rdf:resource="http://opensource.com/law/09/12/ip-another-bubble-about-burst-view-another-civilization"/>
	<rdf:li rdf:resource="http://www.mollerus.net/tom/blog/2010/06/web_app_homescreen_icons_in_android.html"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en/Using_XPCOM_in_JavaScript_without_leaking"/>
	<rdf:li rdf:resource="http://dbaron.org/mozilla/leak-monitor/"/>
	<rdf:li rdf:resource="http://www.emacswiki.org/emacs/MultipleModes"/>
	<rdf:li rdf:resource="http://www.thaiopensource.com/nxml-mode/"/>
	<rdf:li rdf:resource="http://steve-yegge.blogspot.com/2008/03/js2-mode-new-javascript-mode-for-emacs.html"/>
	<rdf:li rdf:resource="http://blogs.msdn.com/cashto/archive/2009/03/31/it-s-ok-not-to-write-unit-tests.aspx"/>
	<rdf:li rdf:resource="http://www.two-sdg.demon.co.uk/curbralan/papers/minimalism/OmitNeedlessCode.html"/>
	<rdf:li rdf:resource="http://www.eecs.harvard.edu/~cduan/technical/git/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://github.com/google/git-appraise">
    <title>GitHub - google/git-appraise: Distributed code review system for Git repos</title>
    <dc:date>2018-02-26T11:55:25+00:00</dc:date>
    <link>https://github.com/google/git-appraise</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[`This tool is a distributed code review system for git repos.

By "distributed", we mean that code reviews are stored inside of the repository as git objects. Every developer on your team has their own copy of the review history that they can push or pull. When pulling, updates from the remote repo are automatically merged by the tool.

This design removes the need for any sort of server-side setup. As a result, this tool can work with any git hosting provider, and the only setup required is installing the client on your workstation.´]]></description>
<dc:subject>git code review appraise distributed tool development practices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:9f25f5f25e4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:review"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:appraise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:tool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:practices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://danluu.com/wat/">
    <title>Normalization of deviance in software: how broken practices become standard</title>
    <dc:date>2017-11-01T07:22:23+00:00</dc:date>
    <link>https://danluu.com/wat/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Very interesting assessment of 'company culture' eventually trumping common sense.  Humans are herd animals.

However, how many of the 'common sense' practices are the product of the culture of Sillicon Valley, where the users of a product number in the hundreds of millions, tolerance for defects is low, and money is readily available to reduce development friction.

On the opposite end of the scale (say a LOB application that has no more than a few dozen users), are all these practices still economically worthwhile?]]></description>
<dc:subject>software practices danluu culture development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:d62b79ce45e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:danluu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://aspiringcraftsman.com/2007/08/25/interactive-application-architecture/">
    <title>Interactive Application Architecture Patterns</title>
    <dc:date>2012-02-19T07:12:07+00:00</dc:date>
    <link>http://aspiringcraftsman.com/2007/08/25/interactive-application-architecture/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[A summary of design patterns for GUI applications that is, at the very least, comprehensive.  Again, none of them convince my gut.]]></description>
<dc:subject>patterns development gui interface</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:f52e491929a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:gui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:interface"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://google-engtools.blogspot.com/">
    <title>Google Engineering Tools</title>
    <dc:date>2012-02-19T06:53:41+00:00</dc:date>
    <link>http://google-engtools.blogspot.com/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Interesting blog that gives a peek about Google's deployment system.  While some things are obviously not relevant to smaller companies, other ideas (such as finding 'hot zones' in code bases) are almost trivial to implement in any organisation.]]></description>
<dc:subject>programming deployment development tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:bde9775d00c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://opensource.com/law/09/12/ip-another-bubble-about-burst-view-another-civilization">
    <title>Is IP another bubble about to burst? A view from another civilization. | opensource.com</title>
    <dc:date>2010-07-24T20:26:54+00:00</dc:date>
    <link>http://opensource.com/law/09/12/ip-another-bubble-about-burst-view-another-civilization</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Article that suggests Indian culture might be more open to open source philosophy than the west.]]></description>
<dc:subject>india software development intellectualproperty</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:6f657035c3f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:india"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:intellectualproperty"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mollerus.net/tom/blog/2010/06/web_app_homescreen_icons_in_android.html">
    <title>Web app homescreen icons in Android (Tom Mollerus' Weblog)</title>
    <dc:date>2010-07-01T16:44:27+00:00</dc:date>
    <link>http://www.mollerus.net/tom/blog/2010/06/web_app_homescreen_icons_in_android.html</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Summary: Android supports the same offline access tags as the iPhone]]></description>
<dc:subject>mobile web development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:4c59a6aa2518/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en/Using_XPCOM_in_JavaScript_without_leaking">
    <title>Using XPCOM in JavaScript without leaking - MDC</title>
    <dc:date>2010-05-28T08:10:29+00:00</dc:date>
    <link>https://developer.mozilla.org/en/Using_XPCOM_in_JavaScript_without_leaking</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... Using XPCOM in JavaScript (also known as XPConnect) is an environment where memory management issues are not obvious. There are no calls to malloc and free and no reference counting. Despite this, it's easy to write JavaScript code that leaks. It's easy to write leaky code in any garbage-collected language. But it's even easier in this environment because some of the objects you're dealing with are reference-counted behind the scenes. ... "]]></description>
<dc:subject>javascript development XPCOM</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:85553d483a16/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:XPCOM"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dbaron.org/mozilla/leak-monitor/">
    <title>Leak Monitor Extension</title>
    <dc:date>2010-05-28T07:58:22+00:00</dc:date>
    <link>http://dbaron.org/mozilla/leak-monitor/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... This Firefox extension detects one very specific type of memory leak in chrome JavaScript and in Web pages. (Not in JavaScript components, though.) It detects when JavaScript objects in the chrome or Web page are still held by native code after the window is closed. It notifies the user after the first full garbage collection (i.e., cycle collection) after the window has been closed, so that the user is most likely to be able to correlate the notification with the action that caused it. ... "]]></description>
<dc:subject>development javascript memory</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:9f7f2d463cc5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:memory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.emacswiki.org/emacs/MultipleModes">
    <title>EmacsWiki: Multiple Modes</title>
    <dc:date>2010-01-27T08:45:03+00:00</dc:date>
    <link>http://www.emacswiki.org/emacs/MultipleModes</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Discusses several approaches for using multiple major-modes in a single buffer (for, for example, literate programming).  'multi-mode' seems to be the most promising approach, as it maintains several 'shadow' buffers behind the scenes to avoid switching modes and keymaps all the time.  It is incompatible with nXML font-locking and (presumably) js2-mode, though.]]></description>
<dc:subject>emacs development editing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:9b8922d0c4ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:editing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.thaiopensource.com/nxml-mode/">
    <title>nXML mode</title>
    <dc:date>2010-01-19T16:01:11+00:00</dc:date>
    <link>http://www.thaiopensource.com/nxml-mode/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Recursive-descent parser based XML editing mode.  Syntax highlighting, and more importantly, support XHTML very well.]]></description>
<dc:subject>xml xhtml editing emacs development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:f73ff876c0d0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:xhtml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://steve-yegge.blogspot.com/2008/03/js2-mode-new-javascript-mode-for-emacs.html">
    <title>Stevey's Blog Rants: js2-mode: a new JavaScript mode for Emacs</title>
    <dc:date>2010-01-19T15:59:22+00:00</dc:date>
    <link>http://steve-yegge.blogspot.com/2008/03/js2-mode-new-javascript-mode-for-emacs.html</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[Recursive-descent parser-based editing mode for emacs.  Does syntax highlighting, shows warnings.  Not as comprehensive as espresso-mode + flymake + jslint, probably, but good enough.]]></description>
<dc:subject>javascript emacs editing ide development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:47de174bae65/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:ide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blogs.msdn.com/cashto/archive/2009/03/31/it-s-ok-not-to-write-unit-tests.aspx">
    <title>cashto's blog : It's OK Not to Write Unit Tests</title>
    <dc:date>2009-11-05T18:12:59+00:00</dc:date>
    <link>http://blogs.msdn.com/cashto/archive/2009/03/31/it-s-ok-not-to-write-unit-tests.aspx</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... Let's be honest. Your tests mostly follow the “happy path”. Sure, on occasion you remember to test “the failure case”—the caller passed in null or a negative integer as an argument—mostly because you just got done writing that check and wouldn't it be a waste not to write a test to show how clever you were? Never mind that null or a negative argument is an assertable precondition that could never happen in production anyways. ... "   The way I've felt for years.  Roland Backhouse had an even more damning critique of testing as a method for catching bugs in one of his books.]]></description>
<dc:subject>programming development testing unittest</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:8ec368b6ca18/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:unittest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.two-sdg.demon.co.uk/curbralan/papers/minimalism/OmitNeedlessCode.html">
    <title>Minimalism: Omit Needless Code</title>
    <dc:date>2009-11-02T18:40:46+00:00</dc:date>
    <link>http://www.two-sdg.demon.co.uk/curbralan/papers/minimalism/OmitNeedlessCode.html</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... Whilst we may muse about engineering, architectural or craft metaphors for software development, there is no denying that, in essence, programming is writing. It is a form of communication that has two distinct audiences: us and the machine. Although there are times when it might not feel this way, the machine is easily pleased, demanding little more than well-formed code. We, however, are a little more complex and discerning: we demand that our communication communicate ... "  A strange, almost political essay about coding style]]></description>
<dc:subject>development programming programming-style</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:9223b75cc8de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming-style"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eecs.harvard.edu/~cduan/technical/git/">
    <title>Understanding Git Conceptually</title>
    <dc:date>2009-09-16T10:23:46+00:00</dc:date>
    <link>http://www.eecs.harvard.edu/~cduan/technical/git/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... The conclusion I draw from this is that you can only really use Git if you understand how Git works. Merely memorizing which commands you should run at what times will work in the short run, but it’s only a matter of time before you get stuck or, worse, break something. ..."  He's right. His conceptual explanation does make git a lot easier to understand.]]></description>
<dc:subject>git tutorial versioncontrol development programming scm</dc:subject>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:abe2245310f9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:scm"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>