<?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>willcodeforfoo</title>
	<atom:link href="http://www.willcodeforfoo.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.willcodeforfoo.com</link>
	<description>a simple technologist&#039;s view of the world</description>
	<lastBuildDate>Thu, 22 Mar 2012 01:44:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Hacking for fun &#8212; capture the flag</title>
		<link>http://www.willcodeforfoo.com/2012/02/capture-the-flag/</link>
		<comments>http://www.willcodeforfoo.com/2012/02/capture-the-flag/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 12:20:58 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[c]]></category>
		<category><![CDATA[ctf]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[low-level]]></category>
		<category><![CDATA[perl]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=132</guid>
		<description><![CDATA[Stripe released their capture the flag game recently https://stripe.com/blog/capture-the-flag and I thought it&#8217;d be a fun exercise to document my entire procedure. So&#8230; before you enter, I warn you&#8230; there are spoilers in here&#8230; Level01 Welcome to Capture the Flag. I, by the way, am not at all affiliated with Stripe, I&#8217;m just an excited [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2012/02/capture-the-flag/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Neotoma &#8211; Super powerful parsing for erlang</title>
		<link>http://www.willcodeforfoo.com/2011/04/neotoma-super-powerful-parsing-for-erlang/</link>
		<comments>http://www.willcodeforfoo.com/2011/04/neotoma-super-powerful-parsing-for-erlang/#comments</comments>
		<pubDate>Thu, 21 Apr 2011 22:45:39 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[erlang]]></category>
		<category><![CDATA[parsing]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=9</guid>
		<description><![CDATA[Erlang strings are painful Oh it&#8217;s so true. The pain is super apparent, especially when trying to parse configuration files. The traditional way to parse a configuration file that is not in the erlang format can be pretty hard to do. For instance, for beehive, the application configuration template looks like: # Config file # [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2011/04/neotoma-super-powerful-parsing-for-erlang/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding a suitable deployment environment</title>
		<link>http://www.willcodeforfoo.com/2011/04/finding-a-suitable-deployment-environment/</link>
		<comments>http://www.willcodeforfoo.com/2011/04/finding-a-suitable-deployment-environment/#comments</comments>
		<pubDate>Sat, 16 Apr 2011 22:44:38 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=4</guid>
		<description><![CDATA[In this new series on my blog, we&#8217;ll look at a few different deployment frameworks (as alternatives to Beehive). VMWare just released their new CloudFoundry framework to the Open-Source world. Obviously, I&#8217;m pretty interested in application deployment, so this clearly piqued my interest. More will follow when I get more experience with CloudFoundry, but here&#8217;s [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2011/04/finding-a-suitable-deployment-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Snow Leopard Erlang woes (and the fix!)</title>
		<link>http://www.willcodeforfoo.com/2009/10/snow-leopard-erlang-woes-and-the-fix/</link>
		<comments>http://www.willcodeforfoo.com/2009/10/snow-leopard-erlang-woes-and-the-fix/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 22:48:12 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=12</guid>
		<description><![CDATA[After upgrading to Snow Leopard, I found my os_mon erlang application exploded in a very ugly error message. =CRASH REPORT==== 12-Oct-2009::23:29:20 === crasher: initial call: memsup:init/1 pid: &#38;lt;0.76.0&#62; registered_name: memsup exception exit: &#123;&#123;badmatch,&#123;error,&#123;fread,input&#125;&#125;&#125;, &#91;&#123;memsup,get_memory_usage,1&#125;, &#123;memsup,'-handle_info/2-fun-0-',2&#125;&#93;&#125; in function gen_server:terminate/6 ancestors: &#91;os_mon_sup,&#38;lt;0.46.0&#62;&#93; messages: &#91;&#93; links: &#91;&#38;lt;0.47.0&#62;&#93; dictionary: &#91;&#93; trap_exit: true status: running heap_size: 233 stack_size: 24 reductions: [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/10/snow-leopard-erlang-woes-and-the-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beehive router architecture</title>
		<link>http://www.willcodeforfoo.com/2009/10/beehive-router-architecture/</link>
		<comments>http://www.willcodeforfoo.com/2009/10/beehive-router-architecture/#comments</comments>
		<pubDate>Mon, 05 Oct 2009 22:55:46 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[code]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=15</guid>
		<description><![CDATA[Introduction Beehive is an open-source application deployment implementation that uses technologies like squashfs, erlang and ruby. It aims to provide a simple, easy application deployment platform. This post will go over the router portion of Beehive. Architecture Beehive is implemented with two servers. One server is the backend server that sits on the nodes that [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/10/beehive-router-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting command-line options into erlang</title>
		<link>http://www.willcodeforfoo.com/2009/10/getting-command-line-options-into-erlang/</link>
		<comments>http://www.willcodeforfoo.com/2009/10/getting-command-line-options-into-erlang/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 22:56:06 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=26</guid>
		<description><![CDATA[So you have your killer erlang application that possibly could make you millions, but it was written in a test environment. Shoot, how do you change that &#8220;on the fly&#8221; at the application runtime? There are a many different ways this can be accomplished. This post will go over the basics of this typical issue. [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/10/getting-command-line-options-into-erlang/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AMQP cake with Ruby: Using Ruby and RabbitMQ together</title>
		<link>http://www.willcodeforfoo.com/2009/08/amqp-cake-with-ruby-using-ruby-and-rabbitmq-together/</link>
		<comments>http://www.willcodeforfoo.com/2009/08/amqp-cake-with-ruby-using-ruby-and-rabbitmq-together/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 22:58:45 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=29</guid>
		<description><![CDATA[There are a bunch of different ways to get connected to RabbitMQ. Thankfully the community has somewhat rallied behind the queue messaging system and there are a growing number of clients/libraries to aid in accessing the queue&#8217;s functionality. In this post, we&#8217;ll explore the different options for connecting a ruby program to the AMQP-driven queue [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/08/amqp-cake-with-ruby-using-ruby-and-rabbitmq-together/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using mochiweb to create a web framework in erlang</title>
		<link>http://www.willcodeforfoo.com/2009/07/using-mochiweb-to-create-a-web-framework-in-erlang/</link>
		<comments>http://www.willcodeforfoo.com/2009/07/using-mochiweb-to-create-a-web-framework-in-erlang/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 22:59:52 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=31</guid>
		<description><![CDATA[Recently, I used Mochiweb for several projects (Alice) I&#8217;ve been working on. After some investigation of the current erlang web frameworks, Mochiweb suited our needs well. It&#8217;s lightweight, fast, open-source and pretty source code. Throughout this post, we&#8217;ll build a little mochiweb application, so note that it will be available in full for download at [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/07/using-mochiweb-to-create-a-web-framework-in-erlang/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Announcing Alice and Wonderland</title>
		<link>http://www.willcodeforfoo.com/2009/07/announcing-alice-and-wonderland/</link>
		<comments>http://www.willcodeforfoo.com/2009/07/announcing-alice-and-wonderland/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 23:02:40 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[alice]]></category>
		<category><![CDATA[erlang]]></category>
		<category><![CDATA[rabbitmq]]></category>
		<category><![CDATA[statistics]]></category>
		<category><![CDATA[wonderland]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=33</guid>
		<description><![CDATA[Alice http://alicetheapp.com. As a queue server, RabbitMQ is super cool, but my company is hesitant to use it without a nice front-end or access to statistics about the server. So we set out to develop the latest RabbitMQ REST interface, Alice. Alice is a RESTful interface to the RabbitMQ server that talks directly through erlang&#8217;s [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/07/announcing-alice-and-wonderland/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Makefiles making erlang easy</title>
		<link>http://www.willcodeforfoo.com/2009/07/makefiles-making-erlang-easy/</link>
		<comments>http://www.willcodeforfoo.com/2009/07/makefiles-making-erlang-easy/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 23:05:12 +0000</pubDate>
		<dc:creator>ari</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.willcodeforfoo.com/?p=42</guid>
		<description><![CDATA[Update (01/04/2010): Added a github repos with a project template for starting new projects here: http://github.com/auser/erlproject_template. The Rakefile in a ruby project is almost just as important as the code itself. Ask any rubyish to show you their project and you can bet your bottom dollar that nine out of every 10 projects of theirs [...]]]></description>
		<wfw:commentRss>http://www.willcodeforfoo.com/2009/07/makefiles-making-erlang-easy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

