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.6 required=5.0 tests=BAYES_05,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uunet!fernwood!portal!cup.portal.com!gamester
From: gamester@cup.portal.com (Lance E Murray)
Newsgroups: comp.lang.ada
Subject: Re: Use pragma INLINE or not?
Message-ID: <43775@cup.portal.com>
Date: 28 Jun 91 17:56:22 GMT
References: <1991Jun19.234429.20796@netcom.COM> <27847@as0c.sei.cmu.edu>
  <3398@sparko.gwu.edu> <1991Jun28.123956.29955@lonex.radc.af.mil>
Organization: The Portal System (TM)
List-Id: <comp.lang.ada>

Thanks for the discussion on this topic. As someone who is monitoring a 
32K line Ada project (using 1750A) I have ran into this same "mentality"
of ..."We don't have time to do analysis, we need to get it coded". 

Although management wants to use this approach to save critical schedule
I've always seen the opposite occur. More time is spent trying to patch
the code (and even patch the patches) than doing it right the first time. 

There seems to be a belief that unless the programmers are coding they are
not working. Therefore, with a push towards Configuration Management, those
in management can see the different releases and feel secure in the 
knowledge that the programmers are "working as hard as they can". The
education system in this country seems to promote the "keep doing it
until it's right" method of software problem solving. There are few,
if any classes taught on how analysis should be performed to find 
what the problems are (i.e, how to fix problem, not symptoms).