The Design Brain in a Technical World

Coding Jargon.

As briefly outlined in my 'about me' section: I'm new to coding. 

As I'm learn the lingo to use, I'm finding it hard not to let the design-side of my brain run rampant with some of these terms. After all, I spent 5 years in design studios learning how to make myself look at new ways of solving problems and coming up with creative solutions in design. Due to this, however, there have been a number of moments in class where I've had to stifle my laughter.

For Example:

On the first day, we were learning about creating "if/else" statements. Basically, if this is true, do the coding that follows. In the event the if statement is not true, you move on to a different option. Any listed possible options that are not the final option are called elsif, short for "or else if". Say "elsif" out loud. My brain (in a rather 'Family Guy'-esque manner) jumped to this:

"Elsif? Do you wanna build some codiiiiiing?"

While working with hashes...

When you are stating the key pair correlation in a hash, you use the characters =>. This is referred to as a "hash rocket".

(This is what I instantly pictured.)

Working with arrays

An array is simply a sequence of information. If I wanted an array of the numbers 1 through 5, it would look like [1,2,3,4,5]. ...which got me thinking...

"Thar be the "Scourge of the Coding Seas", Arrrr."

"Camel Case"

Despite the name, "Camel Case" is WhenYouTypeLikeThis. ...think "humps on a camel" for capitalizing the letters in the string you're typing.

Nothing to do with a place to keep your cigarettes...

Ruby in general

Chris keeps reiterating to us the ease of using Ruby. In many cases, Ruby has the ability to read what you're giving it, and disregard the minor things that may be needed in other programming languages. The most common phrase we keep hearing from Chris: 

Though I'm fully aware Chris was making this reference, it still makes me laugh.

Ultimately

I'm learning to get these terms into my vocabulary. Sure, it may be a bit unique, but I'm sure as hell getting a kick out of it. I plan on keeping track of these mis-haps of coding jargon and occasionally sharing. Until then, enjoy the spoils of my mind running with things it probably shouldn't.

"The best ideas come as jokes. Make your thinking as funny as possible."-David Mackenzie Ogilvy