LabVIEW proverbs!

[altenbach]

---

--- Run Continuously is no way to Run a VI ---

---

(from here)

[Ben]

After reading this post by Jeff I suspect he has been studying at the Rolf Kalbermatter School of Understaements as evidenced by the quote;

And having a 100 second long event case is not really a good idea.

Ben

[JÞB]

OK Ben

---

@Ben wrote:

After reading this post by Jeff I suspect he has been studying at the Rolf Kalbermatter School of Understaements as evidenced by the quote;

And having a 100 second long event case is not really a good idea.

Ben

---

To make proverbs 55:223 official (And run that 55 through Roman numerals)

"The wise LV developer passes commands to actors out of user events while the fool only pounds his unresponsive mouse up and down."

[jcarmody]

---

@Ben wrote:

[...]

When in C point. When in LV, wire.

---

 In a thread discussing In-Place Element Structures​, References and Pointers, Compiler Optimizati​on, and General Stupidity.

[danil33]

USE 'Timing' as a JUICE to a thirsty(greedy) loop!!! 🙂

[AristosQueue (NI)]

I'll offer one that I have handed out a few times:

enum + variant = class hierarchy

identifier string + variant = class hierarchy

enum + flattened data string = class hierarchy

identifier string + flattened data string = class hierarchy

Or, more simply:

type identifier + generic data container = class hierarchy

And "Always buddy your code."

[Eric.M]

Aristos was inspiring me with his ID...

==============================================

Please notify the consumer if the cashier's queue slows down...

==============================================

[AristosQueue (NI)]

One more, this one courtesy of Kurt Grice: "The Object is the Message."

[RavensFan]

From Jeff in this message.

"When your executable can get a driver's license, it's obsolete."

[RavensFan]

"You should never use better and faster to describe a VI with local variables."

-Dennis Knutson, 2014