tbd@neuro.neuro.duke.edu (Tristan Davies) (06/28/91)
As I have browsed the ftp domain and read postings on UseNet, I have become aware that software authors seem to make pre-release prototypes ("beta's?") of their new software available for widespread testing, presumably to unearth bugs. With my voracious appetite for new stuff, I'm wondering what it takes to become one of these testers. Unfortunately, I have no programming experience, so while I might be able to report a bug, I don't think I'd be able to decipher it until I learned more. In any case, I'd be interested to simply learn more about what goes into creating and releasing a new program, so any responses along those lines will be appreciated. Thanks! Tristan "duh..what's a CPU?" Davies e-mail: tbd@neuro.duke.edu Department of Neurobiology, Duke University Medical Center "grblb blabt unt mipt speeb!! oot piffoo blaboo..." -- Opus