03-18-2013 07:50 PM
I will be writing a series of 6 articles over the next few months on top LabVIEW rookie mistakes. Readers will be encouraged to add their own LabVIEW rookie mistakes that they want others to know about to this thread. I also want this to be an open discussion of the article topics so I'll be responding to questions as each new one is released.
No action will be happening with this forum thread now, but subscribe so that when discussions start you can take part.
04-08-2013 11:16 AM
Alright the article is now live (http://zone.ni.com/devzone/cda/pub/p/id/1735).
What are some other mistakes that you've run into that I left off my list?
04-08-2013 11:22 AM
I am so glad you mentioned documentation. I find a lot of the "experts" often forget this. Get people in the habit early and it'll make life a lot easier down the road.
04-08-2013 11:27 AM
I'm planning this as a series of articles where I can dive into each topic more in-depth (no way to fit it all into one article). I purposely put documentation at the end so hopefully I can talk about exciting documentation features in LabVIEW 2013 (shameless LabVIEW Beta plug: ni.com/beta).
I have also found that as programmers (of any language) we wait until the end of development before adding documentation and even then most don't add any at all. This makes it harder than necessary for someone to figure out what your code does. Spending even a little time on documentation can make a world of difference.
04-08-2013 11:28 AM - edited 04-08-2013 11:29 AM
Here is a classic. Not using projects!
The usual answers involve some form of painful experience with projects that grew. Either the developer edits a lot of code outside the project becasue its a quick edit and the project takes time to open. Or the really painful horror case where "It was getting too big" so "We moved things around on disk and cleaned up the vi names." Usually straight drag-n-drops from windows explorer.
That, of course, can really confuse the project and the novice can't explain why, what, when or how to fix it. About that time, the novice just deletes the lvproj file.
04-08-2013 11:33 AM
@JÞB wrote:
Here is a classic. Not using projects!
The usual answers involve some form of painful experience with projects that grew. Either the developer edits a lot of code outside the project becasue its a quick edit and the project takes time to open. Or the really painful horror case where "It was getting too big" so "We moved things around on disk and cleaned up the vi names." Usually straight drag-n-drops from windows explorer.
That, of course, can really confuse the project and the novice can't explain why, what, when or how to fix it. About that time, the novice just deletes the lvproj file.
I haven't seen things go to that extreme. But yes, the lack of projects is a problem. I find this problem grows from working with the very simple projects that don't need to be built. For a few VIs, you can get away with it. But as soon as you get a decently small to medium sized project, project files are a must.
Another issue I just thought of (again, many "experts" fall into this problem): Not handling errors.
04-08-2013 11:51 AM - edited 04-08-2013 11:52 AM
How about not turning on context help?
Or not using the search function?
04-08-2013 12:19 PM
I'd go with billko: not using context help, detailed help or example finder. Some people are very surprised when told about those "features", this can really change their lives 😄
Also:
* I mean - really, if you're a rookie, you don't have a good reason to use stacked sequence, you're just lazy and/or don't know about proper design patterns 😉
04-08-2013 12:23 PM
Awareness of help tools is a big one. There are some people (including myself personally) that feel that Stacked Sequence Structures shouldn't be in the language at all. This is a religious battle though so people will have differing opinions. Expect Stacked Sequence Structures to definitely make an appearance in my Data Flow article.
04-08-2013 12:28 PM
Very nice article.
I received this via email before, but read again.
Actually, this remembers me my first months using LabVIEW: I see wires, I see wires everywhere...
And as Jeff and crossrulz said, not using projects are a risk situation for bigger projects.
Well, every LabVIEW rookie should take a look at this.
Congrats G-Money.