9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: the 'science' in computer scienscience
Date: Tue, 12 Jun 2001 11:09:40 -0400	[thread overview]
Message-ID: <20010612150943.1AD92199E9@mail.cse.psu.edu> (raw)

> Anyway, how do you teach someone to think?  I have no idea; your
> suggestions are a good first step, but it seems that the `proper mind
> set' outcome is a side effect of exposure with that method; is there a
> way to directly target the thought process?

It was imbred in me by a Latin teacher whose key phrase was
``why use two when one will do''.  The immediate application
was to avoid flowery language but it the rule applies in general.

With programming, constraints that helped.  I inherited
a course at Princeton from Rob.  The thing I liked the best about
it was an assignment he gave to write a shell.  The constraint was
in the size of the shell.  We said what it was supposed to do (no
job control) and took points off for programs exceeding the size
limits.  I reviewed the best solutions with the students.

But when it comes down to it, the real challenge is imparting some
flavor of your taste to the students by example or by the application
of grades.  Some rules help, as long as you can get them to understand
that the rules are guidelines and not hard.  If you're lucky you can
do it in such a way that doesn't cramp originality on their part.

I've also found it useful to review Plan 9 code and Unix code with
them.  That way they can see different solutions for the same
problems.  I actually find things like the toy operating system
more harmful than helpful.  They come away understanding some of
the concepts, perhaps better than reading them in a book, but
totally lose the perspective of the size of the problems and
the necessity to be careful with minutia.

All this is very interaction intensive.  It's easy if you're a hired
gun doing one course and then running back to your real life.  I
couldn't imagine keeping it up semester after semester.


             reply	other threads:[~2001-06-12 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 15:09 presotto [this message]
2001-06-12 21:49 ` Dan Cross
2001-06-12 22:50   ` Boyd Roberts
2001-06-12 23:19     ` Jim Choate
2001-06-13 12:22       ` Matt
  -- strict thread matches above, loose matches on Subject: below --
2001-06-12 15:16 anothy
2001-06-12  0:36 presotto
2001-06-12  0:47 ` Boyd Roberts
2001-06-12 14:54 ` Dan Cross
2001-06-13 12:05   ` Toby Thain

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=20010612150943.1AD92199E9@mail.cse.psu.edu \
    --to=presotto@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).