Linked In Icon Twitter Icon Facebook Icon

"interesting to hear views on the subject"

Accovion

Before I start – I just want to emphasize that everyone is entitled to at least one boring Blog post. Well, this is mine. Apologies up front. I did have good intentions, however. I was even going to start it off with some experiences I had in the jungles of South America...
With the new Phuse/FDA collaboration another project starts which will be open source (Working Group “Development of Standard Scripts for Analysis and Programming”). Will this project have a chance or are the barriers too high?
I’m special. In elementary school we had a program called I’m Special.
No points for guessing that the author of this article is a SAS Programmer.
Just in case you all decide to rush off and enter "Frühjahrsmüdigkeit" in google to work out what it is that I am talking about, let me save you the hassle. Literally translated it means something like "spring tiredness"! According to toytowngermany.com Frühjahrsmüdigkeit is another peculiar medical disorder suffered exclusively by Germans! I of course have to disagree.
Personally I cannot understand discussions about creating standard programs or standard macros. I could only imagine very rare situations where standard programs will make more sense than standard macros.
Trainees of today will be the programmers of the future, but is there too much of one global community and not enough of local level support to ensure we have local programmers in the future?
I am a Statistical Programmer, here me roar! That statement sounds very bold and confident; however, to be honest, I am not sure what a Statistical Programmer does anymore. This post may be rehashing some previous topics about specializing or not – but I will try not to be redundant. I want to speak about Statistical Programming – proper.
Specifications are everywhere. Datasets are specified, reports are specified, systems are specified and we all have to deal with the specifications. Often enough we have to create them on our own. But how to make good specifications? Less is more, but is it still enough? What level of detail will fit our requirements?
Lets face it, it does not matter how big or small the organisation you work for is, the chances are that if you are in a programming environment then there is a Good Programming Practice Guideline lurking somewhere not too far behind you. Most likely on a shelf next to long forgotten and out of date SOPs, training documents for out of date processes and manuals for software or equipment you no longer have.
Pages: 1 2