best practices
Avoiding Spaghetti Code in LabVIEW (Part 2)
So, how do you maintain a VI over time, so that it doesn't grow into a huge mess and turn into spaghetti code?