No subject

each other as a group of peers about using it robustly and consistently ...
and now that we are around the corner from 1.0 ... and in the dark bowels of
final integration testing ... the logging system has been INVALUABLE for
figuring out why stuff doesn't work.

Invariably, just given a log ... and a problem report from QA here ... I can
usually narrow in on the source of the problem in the backend without having
to try and reproduce it ...

Over time ... as we have had some people come and go ... and contractors who
were not part of the intial development mantra have worked on the project
... we have had people who "wrote" their code using a debugger ... and
interestingly ... the side effect of that is that when something goes to pot
in the persons code at runtime ... there is generally little if any
information to go on to try and get a handle on what might have gone wrong.

So then ... it must be reproduced ... and in a large scale distributed
system ... reproducing complex scenarios for failure is non deterministic at
best ... and a pain in the A**.

So ... I think the best debugger ... even today ... is good 'ol println()
... IMHO.

My $0.02 ...

Tony(DownWithGUIDebuggersAndIDEs)Pelton

PS. On a RARE occassion ... I have been known to use jdb. I find that this
is a great skill to have ... because when you have a problem in production
... it is typically not acceptable to install your favorite .5GB IDE in
order to do some troubleshooting.

-----Original Message-----
From: Jimmi Dyson [mailto:JimmiD at ILLYCORP.com]
Sent: Thursday, August 17, 2000 5:49 AM
To: advanced-java at xcf.berkeley.edu
Subject: Server-side debugging


Hi all.
I would like to know what you find is the best way to do server-side
debugging. I notice that most of the people on this list are Java purists
(i.e. command line interfaces, non-visual editors) like myself and was
hoping to get some insight into your best practices.
Thank you in advance.

Jimmi Dyson

---
To unsubscribe, mail advanced-java-unsubscribe at xcf.berkeley.edu
To get help, mail advanced-java-help at xcf.berkeley.edu

---
To unsubscribe, mail advanced-java-unsubscribe at xcf.berkeley.edu
To get help, mail advanced-java-help at xcf.berkeley.edu

---
To unsubscribe, mail advanced-java-unsubscribe at xcf.berkeley.edu
To get help, mail advanced-java-help at xcf.berkeley.edu