Songs for the LabVIEW Programmer (songs about LV and the dataflow experience)

From LabVIEW Wiki
Jump to: navigation, search

Last year at the LAVA BBQ here at NI Week, several users -- after a bit of drinking -- discussed the need for some LabVIEW drinking songs. Since NI tries to be responsive to user needs, I started creating songs to meet that need, and pulled on other R&D team members to help out. I already had a couple of children's songs for teaching LV to kids. So for the LAVA BBQ last night, I released Songs For The LabVIEW Programmer. There were only paper print outs available last night. Today I'm posting the songs for everyone to enjoy.

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

Songs For The LabVIEW Programmer Drinking Songs: Songs for singing in groups, particularly while drunk, celebrating LabVIEW. Teaching Songs: Songs for young children, just learning LabVIEW for the first time. Emotional Songs: The angst, the joy, and all the other emotions that programming LabVIEW may raise within the soul.

The Debugging Tune* (to the tune of The Itsy Bitsy Spider**)

The execution highlight goes down the wire route. All along the way, probes may call the data out. If it hits a breakpoint then there it will remain until the Pause button lets the highlight move again!

  • because spiders are good at removing bugs
    • feel free to adapt the original’s hand gestures!

There Was An Old Lady Who Wrote A VI (to the tune of There Was An Old Lady Who Swallowed A Fly)

There was an old lady who wrote a VI. I don’t know why she wrote the VI – it’s a blank VI!

There was an old lady who dropped “Simulate Signal.” I don’t know why she needed the signal – perhaps she just likes a noisy signal? She needed the signal to start the VI. I don’t know why she wrote the VI – perhaps she’s high?

There was an old lady who dropped “Power Spectrum.” I don’t know why she needed the spectrum – perhaps she just pulled it out of her rectum? She needed the spectrum to filter the signal. She needed the signal to start the VI. I don’t know why she wrote the VI – it’s a trivial VI.

There was an old lady who dropped a graph. I don’t know why she needed the graph – perhaps she did it just for a laugh? She needed the graph to display the spectrum. She needed the spectrum to filter the signal. She needed the signal to start the VI. I don’t know why she wrote the VI – to impress a guy?

There was an old lady who dropped a while loop. I don’t know why she needed a loop, why she needed a loop, why she needed a loop, why she – *SLAP*. (Oh, thanks…) She needed the loop to repeat the graph. She needed the graph to display the spectrum. She needed the spectrum to filter the signal. She needed the signal to start the VI. I don’t know why she wrote the VI – it’s a broken VI.

There was an old lady who created a button. I don’t know why she created the button – I’d ask her but she told me not to butt in.

She needed the button to stop the loop.

She needed the loop to repeat the graph. She needed the graph to display the spectrum. She needed the spectrum to filter the signal. She needed the signal to start the VI. I don’t know why she wrote the VI – it’s a familiar VI.

There was an old lady who wrote Acquire-Analyze-Present. And now we know why she wrote the VI: She works for NI!


What Do You Do With A Broken Wire? (to the tune of What Do You Do With A Drunken Sailor?)

CHORUS: What do you do with a broken wire? What do you do with a broken wire? What do you do with a broken wire to fix a broken VI?

Verse 1: Change one of its ends to an indicator! Change one of its ends to an indicator! Change one of its ends to an indicator! That’ll fix the VI!

Verse 2: Insert a node to convert the source type! … That’ll fix the VI!

Verse 3: Check all ends connect to terminals! … That’ll fix the VI!

Verse 4: Use control-B and just remove it! … That’ll fix the VI!

Verse 5: Do whatever the Error Window tells ya! … That’ll fix the VI!

Mary Had A Block Diagram (to the tune of Mary Had A Little Lamb)

Mary had a block diagram

                    block diagram
                    block diagram

Mary had a block diagram

    and she kept adding nodes.

It grew larger than the screen one day

                                        screen one day
                                        screen one day

It grew larger than the screen one day

    which was against the rule.

So Mary created subVIs

                             subVIs
                             subVIs

So Mary created subVIs

    with “Convert To SubVI” tool!


LabInterruptedVIEW (to the tune of An Austrian Went Yodeling)

Ohhh, a programmer launched LabVIEW, a new project begun, When along came a power spike, interrupting the fun. L

Ohhhhhhhhh (lots of pounding on the table) New Class! New V-I! Control+Space! Wire Click! Noooo! (howls)

Oh, a programmer launched LabVIEW, a new project begun, When along came a manager, interrupting the fun. L

Ohhhhhhhhh (lots of pounding on the table) New Class! New V-I! Control+Space! Wire Click! “That would be greaaaat.” Noooo!

Oh, a programmer launched LabVIEW, a new project begun, When along came a forced reboot, interrupting the fun. L

Ohhhhhhhhh (lots of pounding on the table) New Class! New V-I! Control+Space! Wire Click! Dum-du-du-du-duuum! (MS Windows launch sound) “That would be greaaaat.” Noooo!

<and so on, each verse adding another sound or phrase>

LAST VERSE: Oh, a programmer launched LabVIEW, a new project begun, When along came some spare time, and now the VI does run!


The Event Structure (to the tune of Pop Goes The Weasel)

All around the front panel

               the user clicked the mouse

And as it moved or clicked or dragged…

               POP went the events!


Unbreak My VIs by Akash Bhakta (to the tune of Unbreak My Heart by Toni Braxton) http://www.lyricsdomain.com/20/toni_braxton/unbreak_my_heart.html

Un-break my VI Say you can run it again Undo this break that you caused When I broke something else That does not affect my VI Un-open this error list I scrolled so many times Un-break my VI My VI...


LabVIEW Rhapsody (by Stephen Mercer, Christina Rogers, & Jeff Boettcher) (to the tune of Bohemian Rhapsody -- this song is loosely based on a new hire on the LV R&D team breaking LabVIEW.exe when he submits his first feature into the code base. There are a couple of internal terms you should know. "Bowling" is our term for submitting code to Perforce. The "trolls" are project managers who control which developers can submit to Perforce at what times -- they ask questions like, "Have you tested the code? Did you get someone to review it?" AppLibs is the build for the lvrt.dll and InTheDark is the build for LabVIEW RealTime.)

Is this my real job? Is this just fantasy? Working on LabVIEW, Can’t believe they just hired me. Open VIs Look at diagrams in G… We can do better, we need no C routine Because it’s graphical, data flow, Down the wires, into nodes, Every way the code flows, that’s what really matters, in G, in G

Manager, just broke the build. Used Perforce, synch’d to head, Hit submit, and now it’s dead. Manager, the test suite used to run, But now I’ve gone and blown it all away. Manager, oooo, Didn’t mean to make you cry. I’ll have it fixed again this time tomorrow! Carry on, carry on, (as if deadlines really matter…)

Too late, release has come Sends shivers down my spine CAR list growing all the time. OK, everybody, I’ve got to bowl, Just can’t spend any more time to test the code. Mama, oooo, (anyway the code bowls) I don’t want to bowl… I sometimes wish they’d ne’er filed this CAR at all…

The build machine syncs all the files that it can, Incredibuild, Incredibuild – can you make it build faster? InTheDark and Applibs – did you build the realtime? No! LabVIEW linking, LabVIEW linking, LabVIEW linking, LabVIEW linking, LabVIEW linking, here we go – log files show…

I’m just a newbie, nobody told me! He’s just a new grad from college recently… He’ll bring in donuts for this bowl travesty. Easy bug, easy fix – will you let me bowl? Broken Build! No, we will not let you bowl! Let him bowl! Broken Build! We will not let you bowl! Let him bowl! Broken Build! We will not let you bowl! Let me bowl! We will not let you bowl! Let me bowl! Never! Never let you bowl! Let me bowl! Never let you bowl! Oooo No, no, no, no, no, no, YES - Oh mama mia, mama mia, mama mia I can bowl! The manager has given troll permission to me yes me yes me!

So you think you can submit without testing real time? So you think you can bowl and then leave for a while? Oh, baby – can’t do this to our baby. Just back it all out, just back that change right outta here.

Ooh yeah, ooh yeah LabVIEW really matters. Anyone can see LabVIEW really matters – LabVIEW really matters to me

In this way the code bowls…


We did this one in another thread Knight mares: Ben has one there too.

(John lenon Imagine)

Imagine there's no Visual Basic It's easy if you try Only Labview for coding Around us only wires Imagine all the people Living for a day

Imagine there's only blockdiagrams It isn't hard to do Nothing to kill or die for And event structures too Imagine all the people Living life in GUI

You may say that I'm a dreamer But I'm not the only one I hope someday you'll join us And the world will program as one

Imagine written code I wonder if you can No need for probes A brotherhood of man Imagine all the people Sharing all the code

You may say that I'm a dreamer But I'm not the only one I hope someday you'll join us And the world will program as one


As originally presented here

(too, the tune of...."Mary Poppin's" song "Supercalifragilisitexpalidous" )

BE.. cause I was afraid to post when I was new to Lab(VIEW) and Ben, he gave my code a tweak, and told me that I had,(Two) used a local varible that made my VI bad.(oooh) Then Ravens Fan explained to me what I really had(Whoo!)

Ohhhh...

Altenbach, smercurio and nugget for the week... Altenbach, smercurio and nugget for the week... Altenbach, smercurio and nugget for the week... Super class of LVOOP and now my code's not weak!

Hummmm..LabVIEW.ini Hummmmm ditty I Hummmm..LabVIEW.ini Hummmmm ditty I

SO.. as you'll see I'm soon to be an NI gifted Knight And all my LabVIEW code will be just so completely right I'll never miss a single trick my postings are all tight And when I send an app to you it'll sing the bugs goodnight!

OHHHH

Altenbach, smercurio and nugget for the week... Altenbach, smercurio and nugget for the week... Altenbach, smercurio and nugget for the week... Super class of LVOOP and now my code's not weak! ..

(Dick VanDyke- eat your heart out! )