Jump to content

Coding Horror


Recommended Posts

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 ...

Link to post

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...

Link to post
  • 2 weeks later...

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 ...
Link to post

QUOTE (Darren @ Jan 24 2009, 02:08 AM)

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  :yes: .

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.