What Should Computer Scientists Teach to Physical Scientists and Engineers?

  • Authors:
  • Gregory V. Wilson

  • Affiliations:
  • -

  • Venue:
  • IEEE Computational Science & Engineering
  • Year:
  • 1996

Quantified Score

Hi-index 0.00

Visualization

Abstract

Most physical scientists and engineers do not use computers effectively. Whether students in college or professionals working in industry, they write programs from scratch when they could use existing packages, they rarely employ advanced algorithms or data structures in their programs, and they make little use of software tools.Asking physical scientists and engineers to master computer science as well as their own discipline is impractical. Time is one of the scarcest resources in a student's or professional's life; while it is easy to make a list of things that would be useful to know, it is much more difficult to say what should be dropped from existing curricula, or what projects should be postponed or shelved, to make the necessary room.To help clarify the issues involved in deciding what computing skills to teach to physical scientists and engineers, this article presents a thought experiment. Imagine that every new graduate student in science and engineering at your institution, or every new employee in your company's R&D division, has to take an intensive one-week computing course. What would you want that course to cover?The author believes that such a one-week course should (1) concentrate on programming aids, not programming methodology; (2) describe widely available tools, not stand-alone packages; (3) be conservative, that is, be based on tools that have proved themselves and are unlikely to change; and (4) focus on those platforms that practitioners are most likely to have access to. A day-by-day curriculum is outlined.