A wild UC Berkeley CS 61A adventure appears!<p><a href="https:&#x2F;&#x2F;inst.eecs.berkeley.edu&#x2F;~cs61a&#x2F;su13&#x2F;lab&#x2F;lab06a&#x2F;lab06a.txt" rel="nofollow">https:&#x2F;&#x2F;inst.eecs.berkeley.edu&#x2F;~cs61a&#x2F;su13&#x2F;lab&#x2F;lab06a&#x2F;lab06a...</a><p>You can stick your pseudocode into the &quot;give&quot; function: <a href="https:&#x2F;&#x2F;inst.eecs.berkeley.edu&#x2F;~cs61a&#x2F;sp15&#x2F;lab&#x2F;lab10&#x2F;adventure.py" rel="nofollow">https:&#x2F;&#x2F;inst.eecs.berkeley.edu&#x2F;~cs61a&#x2F;sp15&#x2F;lab&#x2F;lab10&#x2F;adventu...</a><p>I&#x27;m not sure it&#x27;s <i>explicit</i> in the original article, but I tend to agree with the sentiment that it&#x27;s a <i>lot</i> more fun to learn about interpreters and databases when you&#x27;re making games rather than corporate infrastructure (although I can&#x27;t deny that building corporate infrastructure has its moments)<p>Joel Spolsky talks about using the compiler to catch errors on p. 68 of &quot;The Best Software Writing I&quot;<p><a href="https:&#x2F;&#x2F;books.google.com&#x2F;books?id=vPvhzDqZlaAC&amp;pg=PA68&amp;lpg=PA68&amp;dq=joel+spolsky+type+compiler&amp;source=bl&amp;ots=cm2hRdP9W5&amp;sig=I3gcA35aUfqoKCcQoiIm-CM6CvY&amp;hl=en&amp;sa=X&amp;ved=0CFUQ6AEwCGoVChMI2YzG6KSUyQIVBcNjCh1oQAcK#v=onepage&amp;q=joel%20spolsky%20type%20compiler&amp;f=false" rel="nofollow">https:&#x2F;&#x2F;books.google.com&#x2F;books?id=vPvhzDqZlaAC&amp;pg=PA68&amp;lpg=P...</a>