In his latest blogpost Refactoring: When Should I Create A SubVI?, James McNally of Wiresmith Technology talks about refactoring and creating SubVIs as a means to clean up code. I especially like his point on Clear and Obvious Coupling when using more SubVIs. As always, he manages to sneak in a reference to unit testing and TDD in general. Thanks, James!
Go read the full article!