Xref: utzoo comp.edu:2676 comp.software-eng:2433
Path: utzoo!attcan!uunet!samsung!ctrsol!cica!iuvax!purdue!bu-cs!xylogics!world!madd
From: madd@world.std.com (jim frost)
Newsgroups: comp.edu,comp.software-eng
Subject: Re: CS education
Message-ID: <1989Nov17.164039.20878@world.std.com>
Date: 17 Nov 89 16:40:39 GMT
References: <7024@hubcap.clemson.edu> <7036@hubcap.clemson.edu> <211@isgtec.UUCP>
Organization: Software Tool & Die
Lines: 31

robert@isgtec.UUCP (Robert Osborne) writes:
>I have seen engineering departments where they hired several community
>college engineering "technicians" and placed them under a VERY good
>professional engineer.  [...]   I see a similiar idea being good in
>computing, where several programmers at a "technician" or community
>college level work with a GOOD computer "scientist", one who has taken
>courses in OS's, compiliers, design theory, etc.

This is an excellent idea, for a variety of reasons.  First, it
familiarizes students with real-life concepts -- complexity, schedule,
communication, and other aspects of real-life that are generally
nonexistent in academic environments.  Second, students who are
recently out of theoretical courses might be able to give an influx of
new ideas or ideas which more jaded programmers have forgotten.  Much
research goes on that real-world programmers miss, often to the
detriment of the general community.  Third, the students will become
excellent targets for hire after graduation.  They already have the
experience and will be familiar with the work in at least one
environment.

As for the relationship between a technician and a scientist, I feel
they should be identical, because the sum of the two is better than
the individuals.  Realistically, however, "There's the way things
should be, and the way things are."  Best we can hope for is to
improve our hit rate :-).

Happy hacking,

jim frost
software tool & die
madd@std.com