home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!goanna!ok
- From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
- Newsgroups: comp.programming
- Subject: Re: Teaching the basics
- Message-ID: <14066@goanna.cs.rmit.oz.au>
- Date: 18 Aug 92 01:06:26 GMT
- References: <1992Aug17.123916.14815@husc13.harvard.edu>
- Organization: Comp Sci, RMIT, Melbourne, Australia
- Lines: 22
-
- In article <1992Aug17.123916.14815@husc13.harvard.edu>, peregrin@husc13.harvard.edu writes:
- > This course is meant to teach students the basics. Even though it
- > is in C, we don't really touch on pointers, and the fanciest thing we teach
- > is recursion (which most don't get anyways).
-
- If you don't know recursion, you don't know programming. It is one of the
- simpler concepts in computing. (Much simpler than mutable variables, IMHO.)
-
- > So if you look around at your fellow programming peers (perhaps the
- > the entry level ones), what basic skills do you wish they were better prepared
- > in? Documenting? Indentation? top-down problem solving? Debugging? Numeric
- > methods? Better understanding of hardware (cpu, terminal i/o)? Efficiency?
- > Engineering skills ? (like kludging vs. recoding; writing code so that it
- > can be maintained in the future; time management; reliability; human
- > interfaces?)
-
- Spelling. Elementary English grammar and usage. Proof-reading (being able
- to look at what you _did_ write and notice when it isn't what you _meant_
- to write). Knowing how to look things up in manuals.
-
- --
- You can lie with statistics ... but not to a statistician.
-