I like Peter Blume and his style, however... When one goes to hire a LV programmer I suggest looking not to just programatic style but interest in at hand project, equipment, experience, etc. Blume became famous for his state machine but I met a programmer of his that had never seen a test sequencer and did not know other styles existed outside state machines. Style is important, and we can learn that from Blume, but that is not the "one and all" of LV programming. One should not look for just style and I think too much emphasis has been placed on style.

So, I read the book the other day and wandered over here from info-labview. My 2 cents: The book is probably the most exhaustive listing of recommendations I've seen. Many recommendations are obvious... after the problem they address has bitten you a few times! A new programmer that is serious about writing good LV code is likely to benefit from this book. Unfortunately, the good "rules" (as the book calls them) are equally presented with what might be more closely called "opinions". While none of the recommendations are outright wrong, some of them made me want to argue ("Use global variables for simple data sharing between parallel loops or Vis", arrrg!). Beginners might have some difficulty in separating one from the other. A bit stronger editing would have been nice. The book is written in what might be called the "classic textbook" style. If walls of text don't thrill you, you might want to skip to the rules summary at the back of the text, and read up on rules that interest you. Overall a worthwhile investment, though it's as expensive as most LV books.