From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Xref: utzoo comp.lang.ada:5822 comp.lang.c++:14351 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!well!nagle From: nagle@well.sf.ca.us (John Nagle) Newsgroups: comp.lang.ada,comp.lang.c++ Subject: Re: chief programmer team organizations was (c++ vs ada results) Message-ID: <25649@well.sf.ca.us> Date: 24 Jun 91 18:29:16 GMT References: <1991Jun18.122812.18190@eua.ericsson.se> <1991Jun18.220609.19103@netcom.COM> <1991Jun19.170047.25064@software.org> <1991Jun20.143535.27176@software.org> <25587@well.sf.ca.us> <1991Jun23.032353.8718@netcom.COM> List-Id: jls@netcom.COM (Jim Showalter) writes: >> Real chief programmer teams are very rare. I've never heard of one >>other than in Brooks' book. >Given your description below, I don't find this surprising, since I >find it impossible. Read on. >>It's organized like a surgical team. The chief >>programmer personally writes most of the delivered code, and everything else > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>is set up to facilitate this. >Tommyrot! How on earth is a single human being going to write "most", >or, for that matter, even a FRACTION, of the code on a project of >significant size? I'm talking here of things like the multi-MILLION >line FAA rewrite of the U.S. air traffic control system. No, what is >needed is a single architect (or at least a very small number of >architects on a tightly focused team) who set up the groundrules for >the overall system. After that, a horde of implementors can hammer >out the individual subsystems. There's a school of thought that if you're writing something that big, your approach is wrong, and you need to develop some abstraction that makes the job smaller and moves most of the specifics into some kind of database. But what Brooks was talking about was a job of the size of an operating system kernel, a compiler, or a typical shrink-wrapped application. Many such jobs are something a single person could write with adequate support; examples of each of the above written by individuals exist. There are also examples of each of the above written by large teams, of course. With respect to the FAA application, it's entirely possible that the whole system will be obsoleted by something that has most of the smarts in the airplanes, perhaps a successor to ACAS with GPS inputs. Articles in Aviation Leak indicate that distributed systems are being worked on, especially for Europe, where cross-border ATC isn't well integrated. John Nagle