home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.edu:1601 comp.lang.misc:2988
- Newsgroups: comp.edu,comp.lang.misc
- Path: sparky!uunet!ftpbox!mothost!merlin.dev.cdx.mot.com!pjd.dev.cdx.mot.com!peterd
- From: peterd@pjd.dev.cdx.mot.com (Peter Desnoyers)
- Subject: Re: Programmers
- Message-ID: <peterd.716085594@pjd.dev.cdx.mot.com>
- Sender: news@merlin.dev.cdx.mot.com (USENET News System)
- Nntp-Posting-Host: pjd.dev.cdx.mot.com
- Organization: Motorola Codex, Canton, Massachusetts
- References: <BuBBoJ.un@rice.edu>
- Date: Thu, 10 Sep 1992 00:39:54 GMT
- Lines: 35
-
- sabry@rice.edu (Amr Sabry) writes:
-
-
- >Many people on this net implied that whoever can write a matrix
- >multiplication subroutine in Fortran is a programmer.
-
- >Based on courses here at Rice University, here is a minimum list of
- >*concepts* that a real programmer should know:
-
- [... deleted ...]
-
- There are a few missing, as far as I can tell:
-
- - introduction to complexity theory. There are a lot of software
- engineers out there who don't know what O(N) means, and it's
- usually not their fault.
-
- - fundamental ideas of computer architecture, so that you know how
- registers, stack frames, and memory (cache & virtual) work, or at
- least how fast they are.
-
- A lot of schools require an assembler course. IMHO, a course
- specifically targeted towards architecture (e.g. MIT 6.004) would
- be better.
-
- - possibly an introduction to databases.
-
- - numerical methods / analysis.
-
- [you know, if we flame long enough we'll probably come up with ACM's
- model curricula. Why don't I just go and pull out my back issues and
- look it up? Because we just moved, and they're in boxes, that's why...]
-
- Peter Desnoyers
- --
-