<?xml version="1.0" encoding="UTF-8"?>
<post>
  <body>@ScroogeMcPump (and anybody interested in learning CS design or Scheme),

Almost nobody uses Scheme outside academia; it's too simplified (most industry uses for such things use its larger parent, lisp).  However, Scheme is a great tool for learning Computer Science; specifically design, but also coding practices, since it's so unlike any language you might already know (or any language you might learn in the future).  The idea is that its uniqueness requires you to actually learn the fundamentals that you might have otherwise (or already) missed without the tendency of falling back to methods you already know.  There are downsides, too; my alma mater changed its entry-level CS course to Scheme, and the students had a &lt;i&gt;miserable&lt;/i&gt; time trying to understand what a &lt;code&gt;for&lt;/code&gt; loop was when they moved to Java for the second course.  While it was a struggle, I think it was probably helpful.  Since Scheme is so totally useless, I think MIT's new(?) method of teaching python in their inro course is preferable (MIT used to use Scheme for that).  The whole idea is to use a simplified version of an easy language to teach the basics, then move to a different language altogether for the more advanced concepts, thus ensuring that the students aren't trapped by a single language upon graduation.  Languages die and get replaced, so you don't want to learn a language in a CS curriculum.  You want to learn design and the flexibility to pick up whatever language-of-the-month the industry is using.

If you're interested in that method and maybe learning with it, I highly recommend the book &lt;a href=&quot;http://www.htdp.org/&quot;&gt;How to Design Programs&lt;/a&gt;, which is freely available online at that link.

&lt;b&gt;&amp;nbsp;&lt;/b&gt;

Oops, that was a really long rant.  ... and yes, my use of &quot;huh&quot; was indeed a jest of sorts.  More importantly, I think it succeeded in its purpose; it's far easier to say &quot;huh&quot; than to say &quot;question mark,&quot; and you likely figured it out pretty quickly.

See also &lt;a href=&quot;http://www.writeteam.com/funny/1997/970423.htm&quot;&gt;a fun poem using such terms&lt;/a&gt;.</body>
  <body-html>&lt;p&gt;@ScroogeMcPump (and anybody interested in learning CS design or Scheme),&lt;/p&gt;

&lt;p&gt;Almost nobody uses Scheme outside academia; it's too simplified (most industry uses for such things use its larger parent, lisp).  However, Scheme is a great tool for learning Computer Science; specifically design, but also coding practices, since it's so unlike any language you might already know (or any language you might learn in the future).  The idea is that its uniqueness requires you to actually learn the fundamentals that you might have otherwise (or already) missed without the tendency of falling back to methods you already know.  There are downsides, too; my alma mater changed its entry-level CS course to Scheme, and the students had a &lt;i&gt;miserable&lt;/i&gt; time trying to understand what a &lt;code&gt;for&lt;/code&gt; loop was when they moved to Java for the second course.  While it was a struggle, I think it was probably helpful.  Since Scheme is so totally useless, I think MIT's new(?) method of teaching python in their inro course is preferable (MIT used to use Scheme for that).  The whole idea is to use a simplified version of an easy language to teach the basics, then move to a different language altogether for the more advanced concepts, thus ensuring that the students aren't trapped by a single language upon graduation.  Languages die and get replaced, so you don't want to learn a language in a CS curriculum.  You want to learn design and the flexibility to pick up whatever language-of-the-month the industry is using.&lt;/p&gt;

&lt;p&gt;If you're interested in that method and maybe learning with it, I highly recommend the book &lt;a href=&quot;http://www.htdp.org/&quot;&gt;How to Design Programs&lt;/a&gt;, which is freely available online at that link.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Oops, that was a really long rant.  ... and yes, my use of &quot;huh&quot; was indeed a jest of sorts.  More importantly, I think it succeeded in its purpose; it's far easier to say &quot;huh&quot; than to say &quot;question mark,&quot; and you likely figured it out pretty quickly.&lt;/p&gt;

&lt;p&gt;See also &lt;a href=&quot;http://www.writeteam.com/funny/1997/970423.htm&quot;&gt;a fun poem using such terms&lt;/a&gt;.&lt;/p&gt;</body-html>
  <created-at type="datetime">2008-11-07T15:54:53Z</created-at>
  <forumable-id type="integer">3</forumable-id>
  <forumable-type>Forum</forumable-type>
  <id type="integer">17221</id>
  <topic-id type="integer">9492</topic-id>
  <updated-at type="datetime">2008-11-07T16:19:03Z</updated-at>
  <user-agent nil="true"></user-agent>
  <user-id type="integer">41779</user-id>
</post>
