TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Nasser Abbasi <[log in to unmask]>
Date:
Thu, 20 Mar 1997 16:06:09 -0800
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=us-ascii
Reply-To:
Nasser Abbasi <[log in to unmask]>
Parts/Attachments:
text/plain (31 lines)
> From [log in to unmask] Thu Mar 20 10:44:01 1997
> Mime-Version: 1.0
> Posting-Date: Thu, 20 Mar 1997 12:07 +0000 (GMT)
> Date: Thu, 20 Mar 1997 12:07:00 +0000
> From: "Pickett, Michael" <[log in to unmask]>
> Subject: Re: Info request: Code development cycle
> To: [log in to unmask]
>
> (I missed the start of this thread because my mail host appears to have lost
> everything since last Friday, but here goes ...)
>
> I interviewed a chap recently, and I asked him about his approach to
> debugging. He told me that he rarely used a debugger, finding it much more
> effective to examine his sources and, from them, to understand why an error
> occurred, rather than poke around to see what was happening.
>
> I discovered that he was ex-army, trained in mine clearance.
>
> Perhaps I should have a word with our training department. :-)
>
> --Michael--

obviously this chap is a good programmer.

very few programmers do desktop inspection of their code, they
would rather spend/waste allot of time in the debugger than just
make a clean print out of the source, and go over the code to try to
see where the problem is.

Nasser

ATOM RSS1 RSS2