Oh, this job is great :-D. It's a similar "style" of job as my old one, in that I'm troubleshooting a third-party vendor's software, but the people here are much more accommodating than my old employer. They're willing to listen to me and consider my approaches in altering functionality and implementing new utilities, which has lead to me developing alternatives to the software's functionality that save tons of time for the users.
I've added a new method for transcription and case alteration that functions in a set-based manner rather than an RBAR manner (users originally had to do one record at a time if they were transcribing; I've implemented an intranet site that allows them to transcribe as many patient records at once as they'd like), and that's increased worker efficiency many times over.
Thanks for asking about my current situation, and many thanks to Mr. Mitchell and Mr. Moden; if I'd limited myself to only trying for jobs that exactly met my abilities, I'd have been stuck in a rut forever. This job was over my head originally, but I've grown into it quite rapidly, and things are looking good :-D
You bet... and it sounds like you've really
hit the ground running. Well done. Thank you for the kind words and the feedback.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs