comp.lang.ada
 help / color / mirror / Atom feed
From: ryer@harp.camb.inmet.com (Mike Ryer)
Subject: Re: Programmers -> Engineers; Engineers -> Programmers
Date: 1996/08/08
Date: 1996-08-08T00:00:00+00:00	[thread overview]
Message-ID: <Dvu0Jr.Esx.0.-s@inmet.camb.inmet.com> (raw)
In-Reply-To: 1996Aug8.115630.4568@relay.nswc.navy.mil


There are many first-rate programmers who have a general scientific education
and the interest and quickness to learn a lot about radar -- just don't let
them design your antennas.  There are many first-rate electronic engineers
who have the patience and flexibility to learn programming -- just don't let
them code your flight control system.

An electrical engineer can learn on his/her own how to program, but it takes
working in a team within an established software engineering culture to really
learn about maintainability, robustness, configuration management, defensive
programming, realtime constraints, etc.  (A succession of hard knocks will
also work, though this is tough on the first few projects).

A good programmer or software engineer should be able to find ambiguities and 
contradictions in the requirements document written by a radar designer, think
of boundary conditions and unusual scenarios, design for efficiency on 
processing the kinds on input that actually occur in practice, etc.  In 
other words, if they're good, they will have insight into the physics, 
electronics, and mechanics of the system.

A successful project wants software engineers who understand the underlying
science, and radar designers who understand software.  At least a few of each.
Maybe you'll find a superman who does quantum mechanics in his head *and*
writes code that's easy for other people to understand.  (I haven't).

To the extent that you don't have the excellent electronic and software
engineers who learn enough about each other's fields, you need communicators,
reviewers, requirements testers as well as code testers (note Arianne 5
story), and a lot of extra time.

So the summary is:  
  Q: Is it better to take engineers/scientists who understand the system
     and teach them how to program?  Or is it better to take programmers
     and teach them about the radar system?
  A: No.

Mike Ryer, speaking for himself, employed by Intermetrics.





  parent reply	other threads:[~1996-08-08  0:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-08  0:00 Programmers -> Engineers; Engineers -> Programmers James Krell
1996-08-08  0:00 ` James A. Krzyzanowski
1996-08-08  0:00 ` Kevin J. Weise
1996-08-10  0:00   ` Andy Askey
1996-08-10  0:00     ` David Weller
1996-08-12  0:00   ` Jack W Scheible
1996-08-12  0:00     ` John Gluth
1996-08-12  0:00     ` Kevin J. Weise
1996-08-14  0:00     ` Robin P. Reagan
1996-08-15  0:00       ` Mike Roske
1996-08-15  0:00     ` James A. Krzyzanowski
1996-08-15  0:00       ` Jack W Scheible
1996-08-15  0:00     ` Alan Brain
1996-08-15  0:00       ` Dale Stanbrough
1996-08-16  0:00       ` steved
1996-08-08  0:00 ` Ron Thompson
1996-08-08  0:00 ` Mike Ryer [this message]
1996-08-09  0:00   ` whiting_ms@corning.com (Matt Whiting)
1996-08-09  0:00 ` Bob Kitzberger
1996-08-09  0:00 ` steved
1996-08-10  0:00 ` Andy Askey
1996-08-13  0:00   ` Frank Manning
1996-08-15  0:00   ` Brendan WALKER
1996-08-11  0:00 ` Jon S Anthony
1996-08-16  0:00 ` Stephen J Bevan
1996-08-16  0:00 ` Jon S Anthony
  -- strict thread matches above, loose matches on Subject: below --
1996-08-14  0:00 Marin David Condic, 407.796.8997, M/S 731-93
1996-08-14  0:00 Marin David Condic, 407.796.8997, M/S 731-93
1996-08-19  0:00 ` Richard Riehle
1996-08-20  0:00   ` Thomas Kendelbacher
1996-08-27  0:00   ` jtapa
1996-08-28  0:00     ` Alan Brain
1996-08-19  0:00 Marin David Condic, 407.796.8997, M/S 731-93
1996-08-21  0:00 ` Jon S Anthony
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox