Leaderboard

I'd have to say that my biggest weakness is that I care too much. I will work and work and work and work until the job is done ahead of schedule and below budget with all expectations exceeded and everyone is happy. Puke!

Generally it is LabVIEWs implementation of OOP. The poor compile times, the complexity, the maintainability, the ballooning of the code base and the bugs. Classical LabVIEW is easy and arguably produces more robust code that is easy to understand for engineers rather than CS academics. I often talk about "pure" and "applied" programmers (an analogue to pure and applied mathematics) and Classical LabVIEW is great for applied programmers. OOP is unnecessary complexity in all but the most fringe use cases and it has sucked all the development resource of the language for features that could have benefitted how a vast majority of production code, that does real things, is written. But no. Interfacing with the windows subsytems, that I'm used to never uses objects. It uses functions in dynamic libraries that take data arguments. Opaque pointers to objects is the quickest way to a GPF and in LabVIEW that means taking out the IDE too. It is only when you get to .NET that you forced to start interfacing with objects and I think you know how unimpressed I am with that-it's banned from my projects. If I want to use .NET I would use C#, not LabVIEW-one advantage of being a polyglot, so to speak, is that I'm not limited to one programming language and can choose the best tool for the job.

This advice may not be much use for your imminent interview, but for the future it may prove useful. If you are looking for a job/career that focuses on using LabVIEW, then you should seriously consider gaining a LabVIEW certification. Certified LabVIEW Developer is the sweet spot. The NI web site has lots of information, including preparation material. Check it out at: http://sine.ni.com/tacs/app/main/p/ap/ov/lang/en/fmid/499