So there is a visual programming language called LabView: http://www.ni.com/labview/ http://www.ni.com/labview/ As a person who really programs, what enevitab

So there is a visual programming language called LabView: http://www.ni.com/labview/ http://www.ni.com/labview/ As a person who really programs, what enevitably happened is systems grew to a complexity (as all systems do that do real work) where real debugging became an issue. So these labview programs made by people who don't program would need debugging...and programmers couldn't really apply 90% of their debugging toolkit to fix the programs, and the non-programmers couldn't fix the programs either. LabWindows ( a C extention to LabView) was a solution that SOMETIMES allowed programmers to make components that would tie in and work in a fine grained manner for the non-programmers to use in LabView, but in the end, the system usually broke down repeatedly. Having programmers make the LV programs wasn't any better, it was very slow, and still suffered from inability to easily spot and fix mis-specification errors, or to gently refine processes. The strangest part about the whole thing is that very small python scripts EASILY replaced all of the LabWindows programs whenever we did that. So we just taught a couple of the engineers a bit of python, had some interns convert the rest, or really moved away from LV as a platform.