Warning for LabVIEW beginners

1. LabVIEW is a programming language, not a drawing tool!
2. Don’t think LabVIEW is simple. Designing a huge project is as difficult as C++!
3. The language itself is always just a move. Please pay attention to cultivating your inner strength: data structure, algorithm, software engineering, digital circuit, etc.!
4. Read more and read good books: "LabVIEW For Everyone", "LabVIEW-Advanced Programming Techniques"!
5. There is only one way to learn programming: read code, write code, read code, write code...!
6. Don’t think you can gain much after reading "LabVIEW For Everyone" once. Please continue to read it twice!
7. Study every example in the book. They are often classics in the program!
8. Align each of your controls and functions, use pop-up menus more often-organize the connections, and don’t let the program look messy!
9. Don’t think you can become a master after reading a few books. Ability is accumulated in the process of doing projects!
10. When you see a LabVIEW program, try to imagine how it is executed in memory!
11. Please pay attention to DLL calls, not every boss is willing to use your product!
12. Read more LabVIEW User Manual, it is the authoritative one!
13. Try to reduce the creation of global variables, it will take up a lot of your memory and time!
14. Try to put unnecessary elements outside the loop!
15. Try to avoid using Build Array in the loop!
16. When speed is extremely important, try to reduce the use of charts or graphics!
17. Name your program with Initialize, not Chushihua!
18. Remember: experts are formed through long-term practice, don't expect to achieve success overnight!
19. Reject impetuousness and patiently read the contents of each section of the book!
20. Programming is an art, pursue the limit of art!
Note: LabVIEW For Everyone is translated as "LabVIEW University Practical Tutorial" published by Electronic Industry Press!

Supplement:
There is another book, the sooner you read it - "The LabVIEW Style", which describes the programming style of LabVIEW. It is authoritative and similar to the Hungarian notation in C language. I heard that some large companies do not use LabVIEW because it is difficult to unify the code style of LabVIEW, and it is difficult to maintain and reuse the code later. This book can make up for this shortcoming to a large extent.
There are also some descriptions of programming style in the built-in help. The sooner you know these rules, the better.