07-15-2022 11:43 AM
@paul_cardinale wrote:
Much of this is specific to my company, but you might find some of it useful.
Thank you for this, it is a great style guide. I had a good laugh at the Coding section where it gives Guideline vs Reason and the first one is:
Don't create obscure or hard to follow code |
Other people will have to deal with your code. |
We are adopting that as out first and only rule from now on!
07-15-2022 12:58 PM
@Jay14159265 wrote:
@paul_cardinale wrote:
Much of this is specific to my company, but you might find some of it useful.
Thank you for this, it is a great style guide. I had a good laugh at the Coding section where it gives Guideline vs Reason and the first one is:
Don't create obscure or hard to follow code
Other people will have to deal with your code.
We are adopting that as out first and only rule from now on!
Maybe you'll like this.
07-15-2022 01:58 PM
@paul_cardinale wrote:
Maybe you'll like this.
Yes, I do like that. Sometimes I work with people that think they are real artists. I wish I could hand them something like this.
07-15-2022 02:14 PM
Don't create obscure or hard to follow code
Other people will have to deal with your code.
We are adopting that as out first and only rule from now on!
Yes, this is why I have been asked to write a coding standard. A former employee's code was soo bad that when I was hired they asked me to write new programs from scratch, even though I had less than a year of experience with labview at the time.
My code probably isn't the greatest but it is readable, commented, and linear flow
I appreciate all the comments!