 |
In trying to define what to teach scientists and engineers about programming in just one week, Gregory V. Wilson has set an extremely ambitious problem. Let me suggest an alternative solution. Given its brevity, a course teaching a minimal body of knowledge for scientists and engineers should stress those aspects most useful in a professional's future employment. In the Summer 1996 issue of IEEE CS&E, the original article by Wilson and the reply by McConnell propose two quite different curricula. The first focuses on the various tasks an engineer must perform, and the second on more fundamental aspects of software engineering. Both are important to teach and both authors make good cases. Rather than add to this discussion, I concentrate on the medium (that is, languages) in which these subjects and principles should be taught. With a proper choice of language, both curricular goals can be achieved.
|
|
For the newest resources, visit Wolfram Repositories and Archives »
