Phillip Brooks Posted January 14, 2009 Report Posted January 14, 2009 Top 25 Most Dangerous Programming Mistakes LabVIEW programmers aren't as concerned as others about the security aspect, but these same mistakes can break your code ... Improper Input Validation Race Condition Untrusted Search Path Improper Resource Shutdown or Release Improper Initialization Quote
PaulG. Posted January 14, 2009 Report Posted January 14, 2009 We should come up with our own "Most Dangerous LabVIEW Programming Mistakes". I would add: Failing to properly close references, using stacked sequences, using globals, messing with a fellow team member's code without permission ... Quote
TobyD Posted January 14, 2009 Report Posted January 14, 2009 QUOTE (PaulG. @ Jan 13 2009, 12:59 PM) messing with a fellow team member's code without permission ... You must have a story to go along with this one Quote
Minh Pham Posted January 15, 2009 Report Posted January 15, 2009 QUOTE (PaulG. @ Jan 14 2009, 07:59 AM) We should come up with our own "Most Dangerous LabVIEW Programming Mistakes". I would add: Failing to properly close references, using stacked sequences, using globals, messing with a fellow team member's code without permission ... Programming without a proper structure/architect --> consequences: can not add new functionalities, hard to maintain, messy code... Quote
Tom Bress Posted January 24, 2009 Report Posted January 24, 2009 How about a list of the "Most Dangerous LabVIEW Programmers"? :laugh: QUOTE (PaulG. @ Jan 13 2009, 03:59 PM) We should come up with our own "Most Dangerous LabVIEW Programming Mistakes". I would add: Failing to properly close references, using stacked sequences, using globals, messing with a fellow team member's code without permission ... Quote
Francois Normandin Posted January 24, 2009 Report Posted January 24, 2009 QUOTE (Tom Bress @ Jan 23 2009, 05:54 PM) How about a list of the "Most Dangerous LabVIEW Programmers"? :laugh: That's likely to include many top posters of LAVA, since they know enough about LabVIEW to be dangerous... Quote
crelf Posted January 24, 2009 Report Posted January 24, 2009 QUOTE (Tom Bress @ Jan 23 2009, 05:54 PM) How about a list of the "Most Dangerous LabVIEW Programmers"? :laugh: Speaking of which, has anyone seen the code in http://decibel.ni.com/content/groups/large-labview-application-development/blog/2009/01/23/architecting-an-application-to-avoid-spaghetti' target="_blank">this article? (btw, the article's a worthwhile read). Quote
Darren Posted January 25, 2009 Report Posted January 25, 2009 QUOTE (crelf @ Jan 23 2009, 05:47 PM) Speaking of which, has anyone seen the code in this article? Hopefully everybody noticed that I wrote that VI 10 years ago. I was in LabVIEW Basics class, and it was my very first LabVIEW app. I assure you the framework I wrote during the CLA last month was much cleaner. -D Quote
jcarmody Posted January 25, 2009 Report Posted January 25, 2009 QUOTE (Darren @ Jan 24 2009, 02:08 AM) I assure you the http://labviewartisan.blogspot.com/2009/01/artisan-sounds-lot-like-architect.html' rel='nofollow' target="_blank">framework I wrote during the CLA last month was much cleaner. This link tells me to: QUOTE Look for some posts in the coming weeks about how I prepared for each exam. I'm looking forward . Quote
crelf Posted January 25, 2009 Report Posted January 25, 2009 QUOTE (Darren @ Jan 24 2009, 02:08 AM) Hopefully everybody noticed that... it was my very first LabVIEW app. I'm just messing with you mate Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.