<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Optera &#187; Tech</title>
	<atom:link href="http://www.optera.net/cat/tech/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.optera.net</link>
	<description>this space intentionally left blank</description>
	<lastBuildDate>Fri, 03 Sep 2010 13:02:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>The Switch Case</title>
		<link>http://www.optera.net/2008/10/switch-case/</link>
		<comments>http://www.optera.net/2008/10/switch-case/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 00:28:57 +0000</pubDate>
		<dc:creator>M. Holger</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Thoughts]]></category>

		<guid isPermaLink="false">http://www.optera.net/?p=43</guid>
		<description><![CDATA[While working on some code recently, I noticed a preponderance — neigh, an outright overabundance — of swith/case logic blocks to control content.  What&#8217;s worse is that the input variable to the switch block happened to be the value of a specific hash key, which got me to thinking — what is the purpose of]]></description>
		<wfw:commentRss>http://www.optera.net/2008/10/switch-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on Code as Data as Code</title>
		<link>http://www.optera.net/2008/06/more-on-code-as-data-as-code/</link>
		<comments>http://www.optera.net/2008/06/more-on-code-as-data-as-code/#comments</comments>
		<pubDate>Thu, 05 Jun 2008 23:54:15 +0000</pubDate>
		<dc:creator>M. Holger</dc:creator>
				<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://www.optera.net/?p=33</guid>
		<description><![CDATA[As an addendum to yesterday&#8217;s little writeup on data-driven design, here&#8217;s another little (perl) trick I&#8217;m particularly fond of, that relies on storing perl code as a hash element. The cool thing about this approach is that you can actually have a configuration file written in, say, XML, that can then reference procedures which are]]></description>
		<wfw:commentRss>http://www.optera.net/2008/06/more-on-code-as-data-as-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Driven Designs</title>
		<link>http://www.optera.net/2008/06/data-driven-designs/</link>
		<comments>http://www.optera.net/2008/06/data-driven-designs/#comments</comments>
		<pubDate>Wed, 04 Jun 2008 21:45:45 +0000</pubDate>
		<dc:creator>M. Holger</dc:creator>
				<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://www.optera.net/?p=32</guid>
		<description><![CDATA[One of the main paradigms I&#8217;m interested in working with when writing new bits of code is the concept of &#8216;data driven&#8217; logic. On the surface this seems simple enough, but for the uninitiated the premise is that one should be able to dictate the logic of a routine via the input data, while doing]]></description>
		<wfw:commentRss>http://www.optera.net/2008/06/data-driven-designs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
