As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.


Here are some tips for How to share your SAS knowledge with your professional network.


Difference between revisions of "Code Like It Matters: Writing Code That's Readable and Shareable"

From sasCommunity
Jump to: navigation, search
(Online materials: switch File: to Media: for direct wikilink)
(Online materials: add MWSUG materials)
Line 12: Line 12:
  
 
== Online materials ==
 
== Online materials ==
 +
* [http://www.mwsug.org/proceedings/2017/TT/MWSUG-2017-TT04.pdf Download the MWSUG 2017 paper]
 +
* [[Media:MWSUG-2017-TT04.pptx|Download the MWSUG 2017 presentation]]
 
* [https://sites.google.com/site/minnesotasasug/meeting-presentations/Kaefer_CodeLikeItMatters.pdf?attredirects=0&d=1 Download the presentation from the MinnSUG July 2017 meeting]
 
* [https://sites.google.com/site/minnesotasasug/meeting-presentations/Kaefer_CodeLikeItMatters.pdf?attredirects=0&d=1 Download the presentation from the MinnSUG July 2017 meeting]
* ''MWSUG 2017 materials coming soon!''
 
 
* [[Media:Sample header.sas|sample_header.sas]], a sample program header as shown on pages 7-8 of the paper
 
* [[Media:Sample header.sas|sample_header.sas]], a sample program header as shown on pages 7-8 of the paper
  

Revision as of 09:24, 11 October 2017

Paul Kaefer

UnitedHealthcare

Minneapolis, Minnesota

Abstract

Coming from a background in computer programming to the world of SAS yields interesting insights and revelations. There are many SAS programmers who are consultants or work individually, sometimes as the sole maintainer of their code. Since SAS code is designed for tasks like data processing and analytics, SAS developers working on teams may use different strategies for collaboration than those used in traditional software engineering.

Whether a programmer works individually, on a team, or on a project basis (delivering code and moving on to the next project), there are a number of best practices that can be leveraged to improve their SAS code. These practices make it easier to read, maintain, and understand/remember why the code is written the way it is.

This paper presents a number of best practices, with examples and suggestions for usage. The reader is encouraged not to apply all the suggestions at once, but to consider them and how they may improve their work or the dynamic of their team.

Online materials

See also