9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: the 'science' in computer scienscience
Date: Tue, 12 Jun 2001 10:54:29 -0400	[thread overview]
Message-ID: <200106121454.KAA08032@augusta.math.psu.edu> (raw)
In-Reply-To: <20010612003610.3980A199E9@mail.cse.psu.edu>

In article <20010612003610.3980A199E9@mail.cse.psu.edu> you write:
>  [...]
>
>This means that we have a hard time imparting anything
>from generation to generation that can really be useful
>except for how to reason about problems.

But knowing how to reason about the problem is a good 75% of the battle
(if not more).  When I was 20 years old, I read, ``The Elements of
Programming Style,'' first edition.  The book is older than I am, but
it _profoundly_ influenced how I thought and worked, even though I've
never programmed in PL/I and only rarely work with FORTRAN.  It was
then that it occured to me that it's the principles, not the specifics,
that are timeless and really important.  The problem with education
these days is that the students want to learn the specifics; mistakenly
assuming that's what's important, and education, hungry for student
currency, is more than happy to cater to them.

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?

	- Dan C.



  parent reply	other threads:[~2001-06-12 14:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:36 presotto
2001-06-12  0:47 ` Boyd Roberts
2001-06-12 14:54 ` Dan Cross [this message]
2001-06-13 12:05   ` Toby Thain
2001-06-12 15:09 presotto
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
2001-06-12 15:16 anothy

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=200106121454.KAA08032@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).