CompuServe Messages

CertDeveloper Betas?

    10-Mar-90 23:15:01
Fm: JAMES D. WILLIAMS 72157,3524
To: Bill Eastburn 70007,1657
What I meant about the construction workers/physicists was that the construction workers were working construction, NOT working as physicists. Sure, there are those working in any field that are very competent but don't have the 'degree'. There are also those with the degree that aren't competent. Both cases are in the minority. And, if we move it back to the subject of developers, yes, there are competent developers that aren't registered with commodore, and there are no err, doubt incompetent developers who are registered… but in _both_ instances they're developers. While a company doesn't need registration to be competent at development, by the same token someone with _no_ experience at development can't be considered competent.While the end-users input might be worthwhile _before_ any work is done on the next revision of the OS, they are _not_ necessarily going to be worth the investment in letting them _test_ the next revision for bugs and flaws. They're input would be exactly what is needed for 'ergonomics' of the next revision, and the time for that is in the design phase, not the implementation/testing phase. When I get a guru 81000009, I know immediately what _kind_ of thing is wrong, not "some weird numbers", and what to check to see if it's the program I'm working with or actually something in the OS. (an example, I'd been getting that particular guru on exit from my program for some time, worrying because it appeared to happen _after_ my program exited… I knew _what_ to look for and _where_ to look for it, and it did turn out to be my code (still using 1.3, btw)). A program I'm beta testing right now (a term program) appears to lock-up at bizarre points. Through experimentation, I've discovered that it is _not_ in fact locking up, but the input/output is getting 'lost'. A 'normal' end-user might possibly have caught this distinction (more likely, not), but, could s/he take it any further? Would s/he know what things to try next time to help narrow down the cause of the bug? again, probably not.