Schmeelkie, its headed that way, anyway.
The end goal of this job is for me to be the data analyst for our clinical research group (we are a little splinter with no official support from the actual Clinical Dept). The R&D scientists will also want to do their own analyses of course, and I as a former scientist will be among them. The Clinical group used to have no access to the data, and that's crazymaking. So my job is to corral the data so we too can play. And because I've been part of the R&D team we work with, I speak the vocabulary, and know the customer better than the younger more clinical-monitor oriented folks in the group.
But... first I have to get the beast built. The beast is new to the company, so its not a matter of finding a buddy and working sidebyside at first. We're all flailing at it together, with different projects.
Its mostly ok, but somedays it makes me crazy. I'd like to avoid SQL but I have a feeling by end of 08 I'll be proficient in it and semi-competent in SAS as well. Ugh Ugh and Ugh.
As I said, there are folks in the Clin Dept who are very helpful - experts in SAS, or in SQL. Originally, there were others with a few months more experience in the beast. However I am now answering as many questions for the latter as they are for me, as I am working in a different direction and getting more hands on experience and planning experience. Its actually a really cool job. Somedays tho, the tasks themselves are either boring or frustrating.
Yes, Tim - you are right for that particular case.
But then on launch days (when we roll it out to a clinical site) its HappyDance all the way!
Altoid - curiously strong.