adamki

##PROTIP: README Love

READMEs are AWESOME. They are one of the best things you can add to a repo, (other than quality code), to make it look professional.

####Things that make a README great:

• A link to the production site on heroku
• A screenshot (or a few) of what the app does (This is especially important if you don't have the production app up and running yet)
• Directions on how to clone or fork the repo and run it locally (explain it like you're explaining things to a totally new programmer)

adamki

• Watch Recursion

• Fork this gist

• Answer the following questions in your fork

  • Do you pronounce 'babel' in the same way? I was watchng with Subtitles and trying to be quiet. Youtube detects his pronuncition as Bubble. I learned not to npm install -g bubble.

    Also, the music is really good in this video.

• Follow Up Question: Will you now?

adamki

Step One: Watch Mary Rose Cook Live Codes Space Invaders from Front-Trends. (The second worst conference name ever?)

Step Two: Fork this gist.

Step Three: Respond to this question in your fork: What is one approach you can take from this Mary's code and implement in your project?

Hands down, the best approach that speaks to me is the tick() function. OUr game time project has a index.js file that is gradually growing larger and larger. I like the idea of having a Game obj and placing a tick function to control drawing and requestAnimationFrame.

adamki

Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)

Step Two: Fork this gist.

Step Three: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).

• Did any of the responsibilities that she lists surprise you?

presentation & interaction data/server communication

adamki

When you start working with WebPack for GameTime, you'll notice that you can't just define a variable in one file and find it in another as easily as you can in Rails.

Read Node.js, Require and Exports and Organize Your Code with RequireJS

Fork this gist and answer the following questions:

• In the context of Node, what is a module? A module is a the essential building block of Node. In node, a module maps directl to a file. The contents of said file are still private and node requires that any access to the files' contents be explicetely returned.

adamki

**Step One**: Watch [Sorting Algorithms in JavaScript](https://www.youtube.com/watch?v=uRyqlhjXYQI)

**Step Two**: Fork this gist.

**Step Three**: Respond to this question in your fork: "What are some of the balances and trade offs between different sorting algoritms?"

Trying NOT to oversimplify this questions, but it is a balnace of Space and Time. Space refers to memory. Time refers to the amount time time consumed while performing a task. 

Jenn describes how Big O is a variable that can be used to measure run time. While handy, this doesn't take into account when SPACE must be taken into consideration. We can use the example of a Space efficient sort (Bubble) contrasted with a time effecient sort(merge). Depending on the use case, and resources, one may choose a slightly slower sort to save space.

adamki

JavaScript Functions

I can explain the difference between function declarations and function expressions. yes

I can explain what the value of this is in a normal function. yes

I can explain what the value of this is when called from the context of an object. yes

adamki

Array Prototype Methods

I understand that functions in JavaScript can take any number of arguments. Yep.

I can describe the similarity between blocks in Ruby and anonymous functions in JavaScript. Yep. Anonymous functions are similar to Ruby Blocks.

Where are the methods available to all arrays (e.g. forEach, map, etc.) defined? Array.prototype.methods

adamki

# Run these with `command + option + n`, NOT `b`


# =====  Toplevel methods are defined where?  =====
def rawr!
  "#{self} says: rawr!"
end
public :rawr!

# *****