Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!netcomsv!jls From: jls@netcom.COM (Jim Showalter) Newsgroups: comp.software-eng Subject: Re: bridge building and discipline Message-ID: <1991May15.180943.6796@netcom.COM> Date: 15 May 91 18:09:43 GMT References: <1991May9.053311.800@netcom.COM> <4563.282e83ea@iccgcc.decnet.ab.com> <1991May14.150350.2837@den.mmc.com> Sender: netnews@netcom.COM (USENET Administration) Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} Lines: 27 Originator: jls@netcom.netcom.com I find it odd that metrics have been successfully used in just about all other industries to improve quality, reduce risk, identify incipient problems, increase productivity, etc, but that many in the software industry feel that metrics cannot do the same for software. The argument appears to be that metrics "cramp" a programmer's "creativity", which seems to be the same argument used against any other attempt to impose some sense of engineering discipline on the "art" of writing software. At root, I think we are in the midst of a paradigm shift, from software as an artistic pursuit to software as an engineered commodity. It is not surprising that those from the old culture do not welcome the shift to the new culture, any more than those with a geocentric model of the universe welcomed the shift to a heliocentric model. Their resistance to the changes manifests itself in a variety of ways, from arguments against software patents ("monopolistic", "stifles free exchange of ideas", etc) to arguments against software metrics and methodologies. But, business is business, and, in the end, things that cost businesses time and money will be displaced by things that improve the bottom line. It will just take time, as do all cultural shifts, particularly since many of those currently managing software projects are themselves products of the culture being displaced. -- **************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 ***************** * Proven solutions to software problems. Consulting and training in all aspects* * of software development. Management/process/methodology. Architecture/design/* * reuse. Quality/productivity. Risk reduction. EFFECTIVE OO techniques. Ada. *