Five Guiding Principles for Hyperion Code Standards and Documentation
Sarah Zumbrum, Finit Solutions
In my decade-long quest to become a better Hyperion code writer, I have seen (and learned) some interesting things. I have seen some beautifully written code, some that I wondered how it worked, some so mangled I thought it would crash and burn if I dared put a space in the line, and some that technically worked but wasn’t efficient. What I have taken away from these experiences is that there should be standard set of code and documenting code so we don’t have to collectively wonder what a set of code is doing. Read more here.
You have to be a member of ODTUG to access Technical Journal articles. There are three membership options, including a free Associate Membership. Join now.
