<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Job on galvanist</title>
    <link>/tags/job/</link>
    <description>Recent content in Job on galvanist</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Aug 2013 01:02:30 +0000</lastBuildDate>
    <atom:link href="/tags/job/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MapStack</title>
      <link>/posts/2013-08-08-mapstack/</link>
      <pubDate>Thu, 08 Aug 2013 01:02:30 +0000</pubDate>
      <guid>/posts/2013-08-08-mapstack/</guid>
      <description>&lt;p&gt;In the San Francisco Bay Area, you have to write a bunch of code to even &lt;em&gt;apply&lt;/em&gt; for I.T. jobs. It doesn&amp;rsquo;t bother me because there is no time pressure and I usually get to work in a language I enjoy on jobs that have tidy solutions.&lt;/p&gt;&#xA;&lt;p&gt;The annoying part is that your work just goes into the bit-bucket, even if (lucky you) you get the job. You can&amp;rsquo;t just publish your solution because then the company would have to come up with a new code challenge. But if you&amp;rsquo;re using the proper level of abstraction, you should be able to publish the reusable bits of your code without spoiling their code challenge.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
