The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] ratfor vibe
Date: Tue, 1 Feb 2022 14:10:09 -0500	[thread overview]
Message-ID: <CAEoi9W5knEaVOrxyFCkj5jGki++065EH1erXL13ByXSgQdtVUw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OwjDOtUOzxPhZinW2o5_LDk5_jD_TZQWgrUSdJF70Xew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

On Tue, Feb 1, 2022 at 1:49 PM Clem Cole <clemc@ccc.com> wrote:

> [snip]
> FWIW:  Through the 60s, the early and into the later 70s, CMU used to call
> its 15-104 "Intro to Computer Programming" and was based on batch (card)
> computing using FTN4, later WATFIV.  They used a number of books.  The book
> I had was from Waterloo and other than being blue and black in color, I
> remember little from it - since I already knew how and the TA let me take
> 'self-taught' by turning in assignments/taking the tests without going to
> class.  Like Freshman Physics and Calc, all intro science and engineering
> majors were required to take it however, since the engineering depts were
> sure what you would see when you graduated was FTN based code [which was
> probably true for the more pure Science types].   Much later (many years
> after I left)  the CS Dept finally convinced Mat Sci, Chem E and Mech E to
> allow the course to be taught using Pascal.  I think they use either Java
> or Python now, but I haven't checked.
>

There was a bit of a stir about 10 years ago when CMU switched from Java (I
think?) to Python and SML for introductory computer science education. I
remember reading a report at the time, which I _think_ is this:
http://reports-archive.adm.cs.cmu.edu/anon/2010/CMU-CS-10-140.pdf

Though perhaps not, because it _really_ bit into Java and the whole OOP
thing.

Robert Harper had a blog post that I found interesting about exposing
freshmen to functional programming:
https://existentialtype.wordpress.com/2011/03/15/teaching-fp-to-freshmen/

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 2261 bytes --]

  reply	other threads:[~2022-02-01 19:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 18:19 Noel Chiappa
2022-02-01 18:47 ` Clem Cole
2022-02-01 19:10   ` Dan Cross [this message]
2022-02-01 19:39     ` Clem Cole
2022-02-01 21:21       ` Dan Cross
2022-02-01 21:33         ` Clem Cole
2022-02-01 23:12           ` John Cowan
2022-02-01 19:39   ` Richard Salz
2022-02-01 22:30   ` Erik E. Fair
2022-02-02  0:54     ` Yeechang Lee
2022-02-01 21:50 ` Win Treese
  -- strict thread matches above, loose matches on Subject: below --
2022-01-31 20:46 Will Senn
2022-02-01 15:37 ` arnold
2022-02-01 15:52   ` Ralph Corderoy
2022-02-01 16:58     ` Clem Cole
2022-02-01 17:02     ` silas poulson
2022-02-02  7:47     ` arnold
2022-02-03 18:57       ` silas poulson
2022-02-04  8:26         ` arnold
2022-02-04 19:41           ` John Cowan
2022-02-10 15:18       ` Ralph Corderoy
2022-02-03  4:00 ` Will Senn
2022-02-03  4:31   ` Al Kossow
2022-02-03  5:16     ` Warner Losh
2022-02-03 20:00   ` Adam Thornton
2022-02-04  6:06     ` Ori Idan
2022-02-04 17:35       ` Adam Thornton
2022-02-04 17:44         ` Will Senn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEoi9W5knEaVOrxyFCkj5jGki++065EH1erXL13ByXSgQdtVUw@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).