"John Larkin" wrote
in message ...
On Fri, 12 Oct 2007 16:14:32 -0400, "robb"
wrote:


"John Larkin"
wrote
in message ...
On Thu, 11 Oct 2007 13:13:59 -0700, "Joel Koltner"
wrote:

There's a secret, seldom-used, nearly foolproof way to avoid
program
bugs, which I will now reveal to the world:

Every time you write a line of code, think about it.

John

Damn John i wish i had not read that !

all those years of using software debugging tools of various
complexities, tedium, exorbitant costs in money and time and
all
i had to do was use the John methodolgy of code construction
the
"T.A.I. method"

now if you could just work some traceability in to that method
along with peer review ideas, some QA stability and QC
measures
then you could sell it

yes it was a joke (partially)
robb


If you're spending more than 15% of your effort debugging, you
should
adopt the T.I.A. methodology.

oh, i was only involved in churn/burn/test/fix/repeat company
once while still in school, because the owner/prez/sales manager
was a play hard and work twice as hard adrenaline junkie.
(results yesterday)

the debugging occured during the legacy systems era, we mostly
debugged third party legacy software
addins/plugins/libraries/toolboxes/etc the ones we were forced to
use and integrate by the pennymeisters

if we were spending 15% debugging our code there would have
been some F.I.A and A.O.D.
(foot in azz / azz out door) methods practiced

i still like the T.A.I. (think about it) method

robb