Refining Scribe
Date: 16/7/2004
I've been hard at work removing some of the more obsure yet damaging bugs in Scribe's back end code. You know the ones that cause weird "write errors" for no apparent reason. Well I'm trying to be diligent and not ignore those at the moment. Because I'd really like to be able to call the next release or 2 the new "stable" build for the next 6 months or so.

Basically the process for debugging these hard to track down bugs, that never happen on my machine, is to put debug output statements through the relevant code to dump information about the state of the program to a file while it runs. And then the user experiencing the problem runs this debug build and sends me the output text file. Which I pour over, wondering why the heck it's breaking. Then I go an stare at the code for hours, change some small thing and send off a new build. Get back a new text file and repeat. Often 4 or 5 times before it becomes obvious whats going on.

This is not the "fun" part of what I do. This is the least fun part. But for the user I do what I must... how noble of me. Ha.

Anyway, I hoping that I won't have to do much more in the short term and that Scribe will be nice and well behaved for everyone. New release soon...
Email (optional): (Will be HTML encoded to evade harvesting)
Remember username and/or email in a cookie.
Notify me of new posts in this thread via email.