home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.edu:1354 comp.lang.fortran:3193
- Newsgroups: comp.edu,comp.lang.fortran
- Path: sparky!uunet!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!lanl!cochiti.lanl.gov!jlg
- From: jlg@cochiti.lanl.gov (Jim Giles)
- Subject: Re: scientists as programmers (was: Small Language Wanted)
- Message-ID: <1992Aug26.155946.3449@newshost.lanl.gov>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- References: <DAVIS.92Aug23010605@pacific.mps.ohio-state.edu> <1992Aug25.034553.2990@linus.mitre.org> <1992Aug25.154501.8654@colorado.edu> <1992Aug25.202307.12365@newshost.lanl.gov> <l9lrciINNb7b@almaak.usc.edu>
- Date: Wed, 26 Aug 1992 15:59:46 GMT
- Lines: 17
-
- In article <l9lrciINNb7b@almaak.usc.edu>, ajayshah@almaak.usc.edu (Ajay Shah) writes:
- |> [...]
- |> I agree with the original poster -- in general good scientists are
- |> focussed on their application areas and simply don't invest in knowing
- |> about computers. Long experience often makes them good coders, but
- |> rarely good programmers. Look at the accent on fortran, for example:
- |> how could a good programmer possibly use fortran? It has to be the
- |> case of a person who wants to get a job done and doesn't take interest
- |> in the means.
-
- A good programmer *can* use *any* language and always picks the one
- best suited to his task (Fortran in the case of scientific/numerical
- work). A good programmer would *never* even use the argument that
- language choice is a measure of *programmer* quality.
-
- --
- J. Giles
-