<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:whatcodecraves.com,2008-08-17</id>
  <link type="text/html" rel="alternate"
  href="http://whatcodecraves.com"/>
  <link type="application/atom+xml" rel="self"
  href="http://www.whatcodecraves.com/articles/atom.xml"/>
  <title>What Code Craves</title>
  <updated>2008-08-17</updated>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/17/week_of_insomnia/</id>
    <published>2008-08-17</published>
    <updated>2008-08-17</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/17/week_of_insomnia/"/>
    <title>Week of Insomnia</title>
    <content type="html"><![CDATA[ 
<p>Contrary to what you might think, I think insomnia's fantastic.  It
puts me in this limbo state where my mind feels like lead and I suck
at <em>almost</em> everything.  One thing I've found myself to be quite good
at is catching up on Internet.  There was plenty of crap, but I found
a lot of good technical stuff.</p>
<p class='read-more'><a href='/articles/2008/08/17/week_of_insomnia'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/13/mini_apps_galore/</id>
    <published>2008-08-13</published>
    <updated>2008-08-13</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/13/mini_apps_galore/"/>
    <title>Mini-apps Galore!</title>
    <content type="html"><![CDATA[ 
<p>I'm warming up to the idea of using small webapps that do <em>less</em>.
Instead of full blown behemoth applications that take a lot of time to
learn and configure, they're more in the spirit of Unix tools or perl
one-liners.  Here's three that I came across that show quite a bit of
promise.</p>
<p class='read-more'><a href='/articles/2008/08/13/mini_apps_galore'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/12/picking_at_capistrano/</id>
    <published>2008-08-12</published>
    <updated>2008-08-12</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/12/picking_at_capistrano/"/>
    <title>Picking at Capistrano</title>
    <content type="html"><![CDATA[ 
<p>Here is the setup I wanted with <a href="http://www.capify.org/">Capistrano</a>
with my <a href="http://housing.whatcodecraves.com/">housing app</a>.  I wanted
to develop locally and continue using Subversion over SSH for source
control.  Meanwhile, Cap would run svn commands remotely with
basic svnserve.  My first configuration looked like this:</p>
<p class='read-more'><a href='/articles/2008/08/12/picking_at_capistrano'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/11/tweaking_apache_with_phusion_passenger/</id>
    <published>2008-08-11</published>
    <updated>2008-08-11</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/11/tweaking_apache_with_phusion_passenger/"/>
    <title>Tweaking Apache with Phusion Passenger</title>
    <content type="html"><![CDATA[ 
<p>Carrying over from weekend cleanup, I started exploring the different
deployment options available.  Here are some bleak notes as I go
along:</p>
<p class='read-more'><a href='/articles/2008/08/11/tweaking_apache_with_phusion_passenger'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/10/debian_ubuntu_specific_rails_with_postgresql/</id>
    <published>2008-08-10</published>
    <updated>2008-08-10</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/10/debian_ubuntu_specific_rails_with_postgresql/"/>
    <title>Debian/Ubuntu Specific Rails with Postgresql</title>
    <content type="html"><![CDATA[ 
<p>I spent the weekend migrating from my shared hosting at Dreamhost over
to VPS hosting at <a href="http://www.silverrack.com/">SilverRack</a>.  In the
move, I setup my housing app to run on postgresql instead of mysql.  I
was in for a few surprises though.</p>
<p class='read-more'><a href='/articles/2008/08/10/debian_ubuntu_specific_rails_with_postgresql'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/07/messy_ruby_requires/</id>
    <published>2008-08-07</published>
    <updated>2008-08-07</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/07/messy_ruby_requires/"/>
    <title>Messy Ruby Requires</title>
    <content type="html"><![CDATA[ 
<p>At some point in tinkering with a language, you outgrow simple scripts
and want to organize your code into separate modules that live in
separate files.  It's just this little OCD code habit you develop.
Since I've only been using Ruby with Rails up till now, loading and
importing the correct library files have been completely hidden away
by Rails convention and magic.  Everytime I want to use a library
named 'acts_as_giraffe', I either A) assumed it was loaded already, or
B) do <tt>require 'acts<em>as</em>giraffe'</tt>.  But the real world's not
so easy.</p>
<p class='read-more'><a href='/articles/2008/08/07/messy_ruby_requires'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/06/flaco_crusher/</id>
    <published>2008-08-06</published>
    <updated>2008-08-06</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/06/flaco_crusher/"/>
    <title>Flaco Crushers</title>
    <content type="html"><![CDATA[ 
<p>Originally, this post was titled 'Ruby Markdown Implementations' and
I was going to talk about
<a href="http://tomayko.com/writings/ruby-markdown-libraries-real-cheap-for-you-two-for-price-of-one">alternatives</a>
to <a href="http://www.deveiate.org/projects/BlueCloth">BlueCloth</a>.  But while
I was reading up about <a href="http://maruku.rubyforge.org/">Maruku</a>, I
followed a link to <a href="http://webgen.rubyforge.org/">webgen</a>.  As if that
wasn't enough, reading up on webgen led me to yet another static site
generator called <a href="http://webby.rubyforge.org/">webby</a>.</p>
<p class='read-more'><a href='/articles/2008/08/06/flaco_crusher'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/05/flaco_rewrite/</id>
    <published>2008-08-05</published>
    <updated>2008-08-05</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/05/flaco_rewrite/"/>
    <title>Flaco Rewrite</title>
    <content type="html"><![CDATA[ 
<p>I've been happily using my own ghetto blog I named <a href="/2008/01/27/flaco_blog">Flaco
Blog</a>.  The beauty of forcing myself to eat my
own software is that I can't really complain about it.  Either
something works exactly as I want it, or it slowly irritates me until
it overcomes the effort needed to rewrite it.  So why am I proposing a
rewrite?</p>
<p class='read-more'><a href='/articles/2008/08/05/flaco_rewrite'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/03/my_keyboard/</id>
    <published>2008-08-03</published>
    <updated>2008-08-03</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/03/my_keyboard/"/>
    <title>My Keyboard</title>
    <content type="html"><![CDATA[ 
<p>... is awesome.  I have the same keyboard at home and at work.  It
does everything that I want a keyboard to do.  It looks fantastic.  It
feels fantastic.  It types fantastic.  And best of all, it does all of
this without any drama.</p>
<p class='read-more'><a href='/articles/2008/08/03/my_keyboard'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/08/02/emacs_info/</id>
    <published>2008-08-02</published>
    <updated>2008-08-02</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/08/02/emacs_info/"/>
    <title>Emacs Info</title>
    <content type="html"><![CDATA[ 
<p>Just a quick cheatsheet of how to get around in Info mode in Emacs.</p>
<p class='read-more'><a href='/articles/2008/08/02/emacs_info'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/30/rails_string_inflections/</id>
    <published>2008-07-30</published>
    <updated>2008-07-30</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/30/rails_string_inflections/"/>
    <title>Rails String Inflections</title>
    <content type="html"><![CDATA[ 
<p>I've been using
<a href="http://api.rubyonrails.org/classes/ActiveSupport/CoreExtensions/String/Inflections.html#M000488">constantize</a>
to turn strings into Class objects.  Constantize is mixed into the
String class by Rails.  This got me to thinking about other clever
helpers that might be mixed into the string class.  A quick search
through the API did not disappoint.</p>
<p class='read-more'><a href='/articles/2008/07/30/rails_string_inflections'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/24/rspecing_acts_as_state_machine/</id>
    <published>2008-07-24</published>
    <updated>2008-07-24</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/24/rspecing_acts_as_state_machine/"/>
    <title>RSpec'ing acts_as_state_machine</title>
    <content type="html"><![CDATA[ 
<p>One of my favorite plugins I've seen so far is
<a href="http://agilewebdevelopment.com/plugins/acts_as_state_machine">acts_as_state_machine</a>.
It's a dead simple way to model the different states your models can be
in.  It also lets you register callbacks to when a model enters,
entered, or leaves a particular state.  It's absolutely fantasic until
I have to test it.  Then it becomes an absolute nightmare.</p>
<p class='read-more'><a href='/articles/2008/07/24/rspecing_acts_as_state_machine'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/18/first_sprint/</id>
    <published>2008-07-18</published>
    <updated>2008-07-18</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/18/first_sprint/"/>
    <title>First Sprint</title>
    <content type="html"><![CDATA[ 
<p>Today at work, I sat in my first <a href="http://en.wikipedia.org/wiki/Planning_poker">planning
poker</a> meeting.  This was
in preparation of our next 4 weeks of development time.  We used the
<a href="http://planningpoker.com/">Planning Poker</a> site to vote on suggested
projects.  I had read a little bit about user stories back in my Rails
class, but the few times I tried practicing agile development
methodologies were always met with whining and criticism.  It's good
to be at a place where people support this.</p>
<p class='read-more'><a href='/articles/2008/07/18/first_sprint'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/15/dangerous_scaffolding/</id>
    <published>2008-07-15</published>
    <updated>2008-07-15</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/15/dangerous_scaffolding/"/>
    <title>Dangerous Scaffolding</title>
    <content type="html"><![CDATA[ 
<p>I did something bad today.  It wasn't bad enough to destroy working
customer instances, but it was enough to make all the dev team all up
in a huff.  The worst part of the whole experience was a) I didn't
remember I was the one who nuked it, and b) it got nuked because of
some crufty scaffolding and default behaviours.</p>
<p class='read-more'><a href='/articles/2008/07/15/dangerous_scaffolding'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/13/capify_my_app/</id>
    <published>2008-07-13</published>
    <updated>2008-07-13</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/13/capify_my_app/"/>
    <title>Capify my App</title>
    <content type="html"><![CDATA[ 
<p>After a complete Saturday of vegging out, I decided to accomplish
something today.  My initial target was to pull Craigslist rental
listings for my <a href="http://housing.whatcodecraves.com/">housing app</a>, but
that led to me learning more about plugins, which somehow led me to
reading about Capistrano.  Yak shave, anyone?</p>
<p class='read-more'><a href='/articles/2008/07/13/capify_my_app'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/09/fuck_fixtures/</id>
    <published>2008-07-09</published>
    <updated>2008-07-09</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/09/fuck_fixtures/"/>
    <title>Fuck Fixtures</title>
    <content type="html"><![CDATA[ 
<p>When you first start testing a newly created application, fixtures
might seem very appealing.  They're easy to write, they make sense,
and they quickly create valid or invalid instances for you to test
with.  Unfortunately, fixtures don't scale with a growing project.
They quickly get out of hand, and you'll end up spending more time
fixing your fixtures than your tests and code.  So fuck you fixtures,
and good riddance.</p>
<p class='read-more'><a href='/articles/2008/07/09/fuck_fixtures'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/07/04/rails_web_engineering/</id>
    <published>2008-07-04</published>
    <updated>2008-07-04</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/07/04/rails_web_engineering/"/>
    <title>Rails Webapp Engineering</title>
    <content type="html"><![CDATA[ 
<p>The day after I came back from Australia, I started my new job at
<a href="http://www.coupa.com">Coupa Software</a>.  I'm absolutely loving it at
the moment because of the awesome people and the amount of software
I'm learning.  Here's just a few that I've picked up in my first week
that I'd like to jot down.</p>
<p class='read-more'><a href='/articles/2008/07/04/rails_web_engineering'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/06/28/platform_of_choice/</id>
    <published>2008-06-28</published>
    <updated>2008-06-28</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/06/28/platform_of_choice/"/>
    <title>Platform of Choice</title>
    <content type="html"><![CDATA[ 
<p>I kept some rants and notes to myself a while back about what I
thought about some of the operating systems I've used and currently
use.  These notes are more about day-to-day usage from the perspective
of a software developer / power user rather than an objective review
of each platform.  I also update these pages with links to my favorite
apps and tricks I've come across.</p>
<p class='read-more'><a href='/articles/2008/06/28/platform_of_choice'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/06/11/fuzz_testing_and_being_a_dick/</id>
    <published>2008-06-11</published>
    <updated>2008-06-11</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/06/11/fuzz_testing_and_being_a_dick/"/>
    <title>Fuzz Testing and Being a Dick</title>
    <content type="html"><![CDATA[ 
<p>I really couldn't help myself with this one.  Someone gave me the
privledge to play around with their pet project, and the first thing I
thought of was to read the HTML, and write a bash loop to spew all
over it.  We both got a kick out of it.</p>
<p class='read-more'><a href='/articles/2008/06/11/fuzz_testing_and_being_a_dick'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/05/20/my_perl/</id>
    <published>2008-05-20</published>
    <updated>2008-05-20</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/05/20/my_perl/"/>
    <title>my $perl;</title>
    <content type="html"><![CDATA[ 
<p>My first exposure to Perl was near the end of high school when I was
working as a computer assistant at the USDA Forest Service.  I really
can't recall the exact gut feeling Perl gave me at the time, but I
imagine it was a mixture of disgust and delight.  A few years later,
near the end of my undergrad career, Perl came back into my life.
Only instead of a few simplistic scripts, Perl was now the core language
for my job.</p>
<p class='read-more'><a href='/articles/2008/05/20/my_perl'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/05/03/kernel_designs/</id>
    <published>2008-05-03</published>
    <updated>2008-05-03</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/05/03/kernel_designs/"/>
    <title>Kernel Designs</title>
    <content type="html"><![CDATA[ 
<p>I really enjoyed my introductory operating systems class at Berkeley.
The class focused on classic high level OS concepts like process
models, virtual memory, concurrency, and more.  To go along with the
material, teams of 4 formed to implement components in a toy OS called
<a href="http://www.cs.washington.edu/homes/tom/nachos/">Nachos</a>.  The purpose
of this was to keep students focused on the concepts rather than wade
through the quagmire that is x86 assembly.</p>
<p class='read-more'><a href='/articles/2008/05/03/kernel_designs'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/04/22/emacs_tips/</id>
    <published>2008-04-22</published>
    <updated>2008-04-22</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/04/22/emacs_tips/"/>
    <title>Emacs Tips</title>
    <content type="html"><![CDATA[ 
<p>Earlier, I wrote a quick into of how to <a href="/articles/2008/02/14/customizing_emacs">customize your
emacs</a>, but then I realized
that I had no running list of cool emacs tricks.  This article sets
out to remedy that with a list of my favorite commands.  It's by no
means complete, so I'll keep adding on to when when I learn more
stuff.  The <a
href="http://www.amazon.com/gp/product/1882114868?ie=UTF8&amp;tag=what0d-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1882114868">Gnu
Emacs Manual</a> is a good reference to flip through from time to time
to learn new tricks.</p>
<p class='read-more'><a href='/articles/2008/04/22/emacs_tips'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/03/12/rails_tips/</id>
    <published>2008-03-12</published>
    <updated>2008-03-12</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/03/12/rails_tips/"/>
    <title>Rails Tips</title>
    <content type="html"><![CDATA[ 
<p>I have started, abandoned, and restarted many pet rails projects.  All
hype aside, I've collected a fair amount of rails idioms.  Whenever I
come across a problem I know I've dealt with in the past, I usually
run a few greps through my past projects to look for an answer.  The
following pages are disorganized tips of things I have done that are
useful.</p>
<p class='read-more'><a href='/articles/2008/03/12/rails_tips'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/03/10/premature_software_testing/</id>
    <published>2008-03-10</published>
    <updated>2008-03-10</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/03/10/premature_software_testing/"/>
    <title>Premature Software Testing</title>
    <content type="html"><![CDATA[ 
<p>I've fallen victim to it a few times now and would like to remind
myself of the causes and consequences.  Don't get me wrong, I love
testing and have attempted/done/failed at it ever since CS61B.  I've
used standardized test frameworks, hackish quickie frameworks from
school, and created my own small frameworks for specific projects.
Testing is a good thing.</p>
<p class='read-more'><a href='/articles/2008/03/10/premature_software_testing'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/02/14/customizing_emacs/</id>
    <published>2008-02-14</published>
    <updated>2008-02-14</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/02/14/customizing_emacs/"/>
    <title>Customizing Emacs</title>
    <content type="html"><![CDATA[ 
<p>My editor of choice is eight megs and constantly swapping.  I didn't
meticulously choose my editor, but rather had one forced upon me
freshman year in CS61A.  Being young and impressionable at the time, I
saw no downsides to the editor and kept using it more and more day
after day.  First it was coding, then notes, then email.  Now four
years later, I'm basically married to my editor, for better or for
worse.  For a complete reference of my .emacs file, see <a href="/articles/2008/02/14/customizing_emacs/emacs-sample.txt">this
link</a>.</p>
<p class='read-more'><a href='/articles/2008/02/14/customizing_emacs'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/02/05/setup_rails_with_postgresql/</id>
    <published>2008-02-05</published>
    <updated>2008-02-05</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/02/05/setup_rails_with_postgresql/"/>
    <title>Setup Rails with Postgresql</title>
    <content type="html"><![CDATA[ 
<p>Everytime I set up a Rails project, there are many braindead steps
that need to be followed.  Instead of doing a web search each time I
need to get an app setup, I follow these simple sequence of
instructions.</p>
<p class='read-more'><a href='/articles/2008/02/05/setup_rails_with_postgresql'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/02/05/css_tips_and_tricks/</id>
    <published>2008-02-05</published>
    <updated>2008-02-05</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/02/05/css_tips_and_tricks/"/>
    <title>CSS Tips and Tricks</title>
    <content type="html"><![CDATA[ 
<p>These aren't organized in any way for now.  Maybe when I collect
enough of them, I'll create a cookbook of some kind.</p>
<p class='read-more'><a href='/articles/2008/02/05/css_tips_and_tricks'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/01/31/infuriating_job_applications/</id>
    <published>2008-01-31</published>
    <updated>2008-01-31</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/01/31/infuriating_job_applications/"/>
    <title>Infuriating Job Applications</title>
    <content type="html"><![CDATA[ 
<p>Spring is in the air, but instead of allergies, I'm seeing my peers
being hit hard by job anxieties.  Thanks to this gloomy weather, I've
been on top of my job applications.  That isn't to say that every day
has been a merry job hunt.  Normally I would've just let the small
things slide, but it's time to be more frank.  When companies come to
a career fair, they have just as much at stake as the people they're
hiring.  What surprises me is how oblivious certain companies are to
how they're damaging their own reputation.  Here's a rundown of what
can use improvement.</p>
<p class='read-more'><a href='/articles/2008/01/31/infuriating_job_applications'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/01/27/flaco_blog/</id>
    <published>2008-01-27</published>
    <updated>2008-01-27</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/01/27/flaco_blog/"/>
    <title>Flaco Blog</title>
    <content type="html"><![CDATA[ 
<p>A while back I was chatting to Arthur and bitching about all the
various blog systems.  To date, I've tried a wide cross section of
them and found them all to be inadequate.  Arthur's proposed solution
was to write his own.  I shied away from that notion until a few days
ago.  Then I finally caved and started thinking about doing my own.</p>
<p class='read-more'><a href='/articles/2008/01/27/flaco_blog'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
  <entry>
    <id>tag:whatcodecraves.com,/articles/2008/01/26/shoot_em_up_debugging/</id>
    <published>2008-01-26</published>
    <updated>2008-01-26</updated>
    <link type="text/html" rel="alternate" href="/articles/2008/01/26/shoot_em_up_debugging/"/>
    <title>Shoot em up Debugging</title>
    <content type="html"><![CDATA[ 
<p>Debugging is like a video game.  Unfortunately, it's the meanest video
game you will ever play.  The objective is to destroy bugs, but each
destroyed bug will only reveal more sinister bugs with more health,
greater mana, and better AI.  After you've smooshed all the trivial
syntax buggers, a whole new species evolves and leaves you fighting a
being as intelligent as yourself.  That fleeting sense of
accomplishment that you felt the first time you vanquished a missing
semicolon quickly melts into a never-ending nightmare of software
maintenance.</p>
<p class='read-more'><a href='/articles/2008/01/26/shoot_em_up_debugging'>Read more</a></p>
 ]]></content>
    <author>
      <name>jch</name>
    </author>
  </entry>
  
</feed>