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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,81cf52699486abe7
X-Google-Attributes: gid103376,public
From: bill@yy
Subject: Re: Ada95 Strengths/Weaknesses.
Date: 1999/09/28
Message-ID: <7sqmk6$1ck3@drn.newsguy.com>#1/1
X-Deja-AN: 530339779
References: <37EED7B8.245C0054@yukyonline.co.yuky>
 <37EF9B98.7F817CC0@pwfl.com> <t7vh8vx6fh.fsf@calumny.jyacc.com>
 <7sqb4r$15d$1@nnrp1.deja.com> <m3ogenur2s.fsf@kiuk0156.chembio.ntnu.no>
Newsgroups: comp.lang.ada
Date: 1999-09-28T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <m3ogenur2s.fsf@kiuk0156.chembio.ntnu.no>, Preben says...
 
>True. Most bugs are discovered _reading_ through the source code
>rather than just testing the software. 

programmers reading the code?? This is a new one.

seriously, one of the biggest problems I see is that many
programmers do NOT read the code. They try something, it failes, jump
into the debugger, set up a test, buy new hardware, hire more testers,
run a profiler, etc.. they do all that, except actualy EXAMINE the code !

How often do you see a programmer make a printout of their code, and
go ask another programmer to code review the code with them?  How often
do you a programmer print their own code and look at it? I mean really
look at it? 

Bill