Notes N1B

Math 10 -- D. C. Smolarski, S.J.
Santa Clara University, Department of Mathematics and Computer Science

Contents

• Nature of Computer Science
• To Do ...
• Planning for Programs

Nature of Computer Science

As a science, Computer Science is a disciplined study of how to make computers do what a person wants them to do and how computers have been used in science. This means learning fundamental programming techniques and learning algorithms. This does not mean using pre-packaged software, but perhaps coming to realize the work that went into developing the software.

There are as many different ways to make use of and study about computers as there are to make use of and study automobilies.

The engineer who designs a more efficient car engine and a body with less drag uses different techniques than someone who uses a car to drive to work. And the "casual" user of a car certainly uses different techniques than someone who is a race car driver. And these individuals certain have a different set of knowledge and skills than a mechanic who can diagnose automotive problems by listening to a car's "ping." Each of these individuals relates to a car in a different way.

Similarly with the world of computers--computer scientists approach computers in a way different from computer engineers, and from those using computers for certain very specific applications. Studying computer science is not learning how to become a computer technicians or a web site designer, although that may come after someone learns very specialized information.

To Do ...

1. Read Unix Web pages.
2. Do Emacs Tutorial.
3. Redo Demo (on reverse of Appendix Sheet).

You will not be examined on

• Unix (operating system)
• Emacs (editor/ word processor)

Planning for Programs

My suggestions:

• 6th day BEFORE due date of program:
  think about and write code by hand on paper (or at least general outline).
• 5th day BEFORE due date of program:
  type the code into a file on the machine.
• 4th day:
  eliminate compiler errors.
  (i.e., get all the language syntax correct)
• 3rd day:
  eliminate run-time errors.
  (i.e., make sure the program runs to completion)
• 2nd day:
  eliminate logic errors.
  (i.e., make sure your answers are correct)
• Day before:
  (1) Check for enough comments in the code;
  (2) Check for correct output format.
• Day due:
  Turn program in without suffering a nervous breakdown.

This page is maintained by Dennis C. Smolarski, S.J. dsmolarski@math.scu.edu
© Copyright 1998 Dennis C. Smolarski, SJ, All rights reserved.
Last changed: 15 September 1999. Minor typographical change: 11 September 2000.