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=1.9 required=5.0 tests=BAYES_50,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Xref: utzoo comp.lang.ada:5810 comp.lang.c++:14341 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uvaarpa!vger.nsu.edu!g_harrison From: g_harrison@vger.nsu.edu (George C. Harrison, Norfolk State University) Newsgroups: comp.lang.ada,comp.lang.c++ Subject: Re: chief programmer team organizations was (c++ vs ada results) Message-ID: <1107.286584f0@vger.nsu.edu> Date: 24 Jun 91 09:36:48 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> List-Id: In article <25587@well.sf.ca.us>, nagle@well.sf.ca.us (John Nagle) writes: > Real chief programmer teams are very rare. I've never heard of one > other than in Brooks' book. It's very different than having a lead programmer > or a system architect. It's organized like a surgical team. The chief > [etc.] > > It's too much of a culture shock for most organization. > > John Nagle Real life success stories are more than welcome to this Software Engineering Teacher-type. I've found that Brooks' book seems to place all teams in some sort of Shangri-La, where managers are infinitely knowlegable and respect their programmers, customers are always happy, etc. Do chief programmer teams really work anywhere outside of a university classroom or in an experimental industrial setting? George C. Harrison, Professor of Computer Science Norfolk State University, 2401 Corprew Avenue, Norfolk VA 23504 Internet: g_harrison@vger.nsu.edu Phone: 804-683-8654