This is Hooovahh

[Hooovahh]

Customer 1: This is Hooovahh he is the lead developer on the test application written in LabVIEW.

Customer 2: Oh LabVIEW! So you're the guy that writes the VI.

Me: ...the VI?

Just thought I'd share a conversation I had a few years ago before I forget it.

[crossrulz]

---

@Hooovahh wrote:

Me: ...the VI?

---

the VI?  Which of the thousands in this application are you referring to?  That's right.  THE APPLICATION.

I feel your pain.

[Hooovahh]

Thanks for your sympathy. Needless to say I'm a little more sceptical now when someone tells me they "know LabVIEW".

[altenbach]

Well, you could argue that a LabVIEW application typically is a Virtual Instrument in the more generic sense. 😄

[JackDunaway]

Yes! Calling a VI a Virtual Instrument is a skeuomorphism that carries around baggage that can make it tough to understand the general purpose language LabVIEW. Lots of cognitive and logistic overheard involved with, e.g., requiring every single VI to have both a FP and a BD.

[Hornless.Rhino]

---

@Hooovahh wrote:

Thanks for your sympathy. Needless to say I'm a little more sceptical now when someone tells me they "know LabVIEW".

---

I wonder if that would work as a pickup line.

"Hey baby.... I know LabVIEW". 😛

[Hooovahh]

---

@Hornless.Rhino wrote:

---

@Hooovahh wrote:

Thanks for your sympathy. Needless to say I'm a little more sceptical now when someone tells me they "know LabVIEW".

---

I wonder if that would work as a pickup line.

"Hey baby.... I know LabVIEW". 😛

---

"Wanna see my Virtual Instrument?"

"Wanna see my snippet?"

"Do you like my auto-tool?"

[Intaris]

"We can crash at my place"

[Hooovahh]

"It's okay baby, error reports happen to alot of guys."

I feel like we need to make a new thread of, LabVIEW/NI phrases that can have multiple meanings.

[Eden_S]

"I feel like we need to make a new thread of, LabVIEW/NI phrases that can have multiple meanings."

NIuendos?