On Mon, 13 May 2019 at 18:42, Bill Igoe wrote:
>
> In a prop shop long ago , I also emailed all exception messages. It is a
> great way to correct logic errors and capture potentially sloppy code.
> Graphing the errors resulted in an exponential decline in errors.
>
> I also developed a handy per
You could do that with Log4j today ;-)
Gary
On Mon, May 13, 2019, 13:42 Bill Igoe wrote:
> In a prop shop long ago , I also emailed all exception messages. It is a
> great way to correct logic errors and capture potentially sloppy code.
> Graphing the errors resulted in an exponential decline
In a prop shop long ago , I also emailed all exception messages. It is a
great way to correct logic errors and capture potentially sloppy code.
Graphing the errors resulted in an exponential decline in errors.
I also developed a handy performance tracker for critical algorithms and
saved those re
> On 11 May 2019, at 23:25, Alex Herbert wrote:
>
>
>
>> On 11 May 2019, at 22:58, Gilles Sadowski wrote:
>>
>> Le sam. 11 mai 2019 à 23:32, Alex Herbert a écrit
>> :
>>>
>>>
>>>
On 10 May 2019, at 15:07, Gilles Sadowski wrote:
Hi.
Le ven. 10 mai 2019 à 15:5
