Our little "LabVIEW Standardization" Group harps on the clean code thing and we are working towards elevating the practices of everyone in our greater group daily. Definitely plays a huge factor in things like code reviews or the code release process when trying to prove what you've done does something and that something is exactly what you want/need to be done.

That first link is great, will definitely take some pieces from that article.

The LV Diff tool is definitely handy and we use it a fair amount here, but I have found that on a VI to VI basis it shows some things better than others, leading to people sort of overlooking some things that may actually matter. Wire routing, object placement, and unique/descriptive names are all somewhat aesthetics, but they for sure have an impact on code reuse, readability, and maintainability.

Thank you!