Bill Walton wrote: > >Indeed it does. Thanks. > >I would like very much to become involved, but make no pretenses about being >able to contribute as a developer. I've been managing projects / products / >programs / people for the last 15 years. "Back in the day" I was judged to >be a good technical hand (C, Basic, and X86 Assembler), but I've only >recently begun working on getting my programming skills back (now working on >learning Java). > > don't worry I know how you feel. My background was in C, Motorola assembler and real-time kernels...
>My experience tells me, though, that there's always lots of "grunt work" to >be done in bringing a product to market. Testing and documentation are two >skills I can still credibly claim to have, and I'd be very happy to >contribute in those areas. Or any other areas where having some outside >help would let the developers remain focused on producing working code. > > You are right, and actually, having someone think about test plans and construct test cases / procedures would be a very useful thing. We would need to dicuss how to do this exactly (in my background we documented such things as IEEE test plan/test procedure/test cases - for system testing that is). Even just basic testing on various machine architectures we don't have access to, or debugging help pages (or maybe even writing them?) - there are many many things that need doing. We will do our best to organise things just enough to make best use of other's time and resources. Personally, I don't underestimate the value of any of these tasks, and am sure the varied skill-base and knowledge-base represented by this group will help the effort immeasurably. One of the main things is that the development is 'kept honest' for clinicians - i.e. can always be shown to deliver direct and tangible benefits to clinical practice. - thomas - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
