[comp.arch] Teaching Programming

amos@taux01.nsc.com (Amos Shapir) (07/24/90)

In article <13392@cbmvax.commodore.com> jesup@cbmvax (Randell Jesup) writes:
|
|	Most often programs written by undergrads are throw-aways
|(fairly often grads too), and they're taught little of software engineering,
|maintenance, etc that they'll need to know in industry.  Regardless of the
|rhetoric about modularity, etc, many CS undergrads come out coding like
|"fortran" programmers (insert your favorite spaghetti-code language for
|fortran if you wish).  I've seen it happen, with students with 3.x averages
|from a _good_ technical school.  If they're good they'll pick it up, but
|what the hell were they being taught?
|

As I remember from the time I learned to program, the problem was not
following the rules; it was understanding what the rules are for.
Unfortunately, such understanding can only come from maintaining the
same project for a few months - which is longer than the average
programming course.

-- 
	Amos Shapir		amos@taux01.nsc.com, amos@nsc.nsc.com
National Semiconductor (Israel) P.O.B. 3007, Herzlia 46104, Israel
Tel. +972 52 522408  TWX: 33691, fax: +972-52-558322 GEO: 34 48 E / 32 10 N