Thanks Greg. I'll take a look.
I'd also like to thank you for being patient and helpful even with those who have been frustrated with LabVIEW and those who expressed their frustration in unpleasant ways (which possibly included me). I also read one of your posts that addresses my question of the applicability of LabVIEW knowledge. It was in the thread
Teams happy with Wind River Workbench...
Quote:
|
Originally Posted by Greg McKaskle
My point is that the typical LV user wouldn't list their title as a LV programmer. They are a technician, engineer, scientist, or researcher doing some task, and the computer and LV are a tool they use to get their job done. Some jobs naturally call for specialization, others become common tasks such that the original job all but disappears as everyone learns the skill. Computers have evolved so that they are no longer back room devices with specialists keeping them humming. If computer languages evolve the right way, programming will follow a similar path. NI's goal is to provide tools to the engineering masses rather than the specialist?
|
This shed a lot of light on NI is doing with LabVIEW. If it was for the generalist, it would explain my initial frustration because I would be the specialist, but it's okay to be either! I can say that I respect all of you at NI for taking the time to make this tool. After having taught people with no programming experience how to program, I understand how hard it is to teach programming. I would say that LabVIEW is probably easier to learn for someone new at programming; the reason I find C++ much easier to understand is because of my years of programming experience, and I can't expect a new programmer to see things like I see them. Those who look at LabVIEW and go "What! Graphical programming?! That's for NOOBS!!!!" are entirely missing that point.