<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>Pretzel Wisdom</title>
	<link>http://www.pretzelwisdom.com</link>
	<description>This space left intentionally blank?</description>
	<lastBuildDate>Fri, 07 May 2010 02:29:19 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>I&#8217;m Not Smart Enough</title>
		<description><![CDATA[Recently, I needed to write a fairly complex class that had to be as lock-free as possible. While the code wouldn&#8217;t have ended up being too simple if I had written it using a regular, high-level lock (such as a read/write lock), it was quite complex with lock-free semantics, as I had to design a [...]]]></description>
		<link>http://www.pretzelwisdom.com/2009/02/im-not-smart-enough/</link>
			</item>
	<item>
		<title>Wonder Where He Was Looking</title>
		<description><![CDATA[That&#8217;s quite a stare.
(via Gruber, via The Singapore Grand Prix &#8211; The Big Picture &#8211; Boston.com)


]]></description>
		<link>http://www.pretzelwisdom.com/2008/09/wonder-where-he-was-looking/</link>
			</item>
	<item>
		<title>Stand In Line</title>
		<description><![CDATA[How long would you have to wait? See you there in 11-16 years!
(via Panda, via Reason Magazine)


]]></description>
		<link>http://www.pretzelwisdom.com/2008/09/stand-in-line/</link>
			</item>
	<item>
		<title>Samurai Principle</title>
		<description><![CDATA[I came across an interesting discussion on programming.reddit (the original link and the resulting discussion) about whether or not to use status code as return values to indicate success/failure, as opposed to using exceptions to indicate, well, exceptional cases.
I won&#8217;t repeat the pros and cons of either approach, as smarter people than me have done [...]]]></description>
		<link>http://www.pretzelwisdom.com/2008/09/samurai-principle/</link>
			</item>
</channel>
</rss>
