Good Programming Practice

From PhUSE Wiki
Jump to: navigation, search

NEW!! May 2013

In 2012, the Steering Board for Good Programming Practice in Health and Life Sciences (GPP Board) initiated a study to assess the state of programming practices in health and life sciences organizations and the results from the first twenty participants are now available here.

The respondents represent a range of organizations, including pharmaceutical companies, biotechnology companies, CROs and consultancies. 70% of respondents had a GPP document to follow such as a guideline or SOP and of these, 80% were mandatory.

The GPP Board would like to thank all those who have responded so far and invite those who have not responded to take part in this ongoing study. Information about the study along with a participation link can be found on the Good Programming Practice page of the PhUSE wiki.

Contents


Introduction

Good Programming Practice (GPP) is important within the life sciences and healthcare industries as an increased need for efficiency means that code that is clear, easy to maintain and efficient is more important than ever. Efficient code and best practices should not conflict with one another. It is essential to have various guidelines to govern and regulate code on clarity, efficiency, re-usability, adaptability and robustness.

Good Programming Practices :

What is GPP

Some examples of GPP from the above definition:

  • Use of headers
  • Comments
  • Self documenting code
  • Style conventions (such as indenting, clear definition of datasteps and procedures)
  • Dynamic programming- writing programs to accommodate potential changes to data or specifications.
  • Test first design

Articles on Good Programming Practice

Quick guide to GPP courtesy of Shafi Consultancy

The Steering Board for Good Programming Practice (GPP BOARD)

design appropriate use of macros and level of macros hard coding policy naming convention conservative strategies etc….

A key aim of the GPP board is to achieve a consensus recommendations for a consolidated guideline which could potentially replace these documents.

Click on this link for more information on GPP Steering Board.


Several of the boards key objectives relate to the PhUSE wiki.

  1. We are looking to establish a formal set of guidelines for GPP
  2. We want to establish a collection of ideas, opinions and hints and tips for GPP

Study on Good Programming Practices in Health and Life Sciences

Through this first study on GPP in health and life sciences, we are looking to understand

If so-


Click on this link for more information about the study.

Or click on this link to go directly to the study registration https://www.surveymonkey.com/s/GPPSURVEY

How can you contribute?

  1. Add a new wiki page on a GPP topic. (Put the text [[Category:Good Programming Practice]] at the end of the article to enable searching for GPP)
  2. Make updates to existing pages
  3. If you have a brief comment or idea to contribute, please add to the talk page for the wiki.
  4. Get involved with the GPP board. We are currently welcoming new members.

This is the place to share your ideas and post your contributions. Feel free to comment. We need your input!


Bibliography

Some useful further reading on GPP

Kirk Lafler Shares 25 Coding Techniques! 25 Best Practice Coding Techniques for SAS Users
Programming Guidelines (Lewin, L)

Good Programming Practices in SAS (Ford, J 2009)

Good Programming Practice in R (Maechler, 2004)

What Makes a Good Program? (Grundy, D 2010)

Macro Programming Best Practices:
Programming for Job Security Revisited

Writing Test Aware Programs

Nobody voted on this yet
 You need to enable JavaScript to vote
Personal tools
Namespaces
Variants
Actions
Navigation
Projects
PhUSE Wiki Help
Toolbox