I worked at NI for two years out of college. Almost everyone in my cohort has never used it and after training most legit were convinced it was going to take over the world. Internally the juice is strong.
I ended up working as an “applications engineer” which is a glorified way to say “support”. And I saw some really gnarly code. Just literally spaghetti.
I think though the big problem with much of the bad code is that it wasn’t architected and modularized (at all). As the tool is sold as “it’s so intuitively obvious anyone can use it”
I don’t think many people train to use it the same way we were trained. That’s a big bit of the problem.
Hell is always someone else’s code, but if I every had to refactor some labview today, one of the first tools I would reach for would be state machines.
Speaking as someone who used to think this stuff mattered, then realized they’d just been wasting their life, instead of isomorphically rearranging thinking patterns on the deck of the trendtanic.
I ended up working as an “applications engineer” which is a glorified way to say “support”. And I saw some really gnarly code. Just literally spaghetti.
I think though the big problem with much of the bad code is that it wasn’t architected and modularized (at all). As the tool is sold as “it’s so intuitively obvious anyone can use it”
I don’t think many people train to use it the same way we were trained. That’s a big bit of the problem.
Hell is always someone else’s code, but if I every had to refactor some labview today, one of the first tools I would reach for would be state machines.