Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!gatech!gitpyr!scott
From: scott@gitpyr.UUCP
Newsgroups: comp.lang.misc,comp.edu
Subject: Re: How to teach computers
Message-ID: <2980@gitpyr.gatech.EDU>
Date: Thu, 29-Jan-87 19:12:46 EST
Article-I.D.: gitpyr.2980
Posted: Thu Jan 29 19:12:46 1987
Date-Received: Sat, 31-Jan-87 01:56:36 EST
References: <2030@batcomputer.tn.cornell.edu> <269@rabbit1.UUCP> <12556@cca.CCA.COM>
Reply-To: scott@gitpyr.UUCP (Scott Holt)
Organization: Drunken Frat Boys, Inc.
Lines: 28
Xref: watmath comp.lang.misc:213 comp.edu:72


	I once heard an idea from a professor of mine: teach them the
theory first, save the programming till later. The more I think of this
the better I think it is. 
        In a typical beginning computer science course, you are given
a programming language and taught how to use it. Usually by examples of
particular problems solved in the language. Basicly, you are being 
taught `this is how you do such and such in this language.' I think
a much better approach would to first teach them what types of things
are typicly done. Teach them the basics of problem solving, algorithms
problem decomposition, etc. Once they know how to formulate solutions to
problems, they will begin to ask the question `how can I implement this
solution in this language?'. Then give them the programming language, or
maybe even their choice. Then they can see languages for what they
are worth, they will be able to see the strong and weak points of the
different programming languages. They will begin to see programming as
a tool and not a discipline ... and will be able to chose the best tool
for the job they want to do, not just the one they are most familiar 
with.

				- Scott Holt
------------

-- 
So this is the earth...big fat hairy deal.
Scott Holt at Ga. Tech.
ARPA: scott@pyr.ocs.gatech.edu  BITNET: ccastsh@gitvm1
uucp: ...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!scott