rickbacci

Mac OS X 10.10 Yosemite

Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.

This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.

You are encouraged to fork this and modify it to your heart's content to match your own needs.

Install Software

rickbacci

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

rickbacci

Array Prototype Methods

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

I can describe the similarity between blocks in Ruby and anonymous functions in JavaScript. 3

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

I can explain the difference between using a for loop and the forEach method. 3

rickbacci

**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?"

Insertion sort is quicker, and uses less resources when the data is nearly sorted. Very slow if the data is reverse ordered.
Bubble sort is easy to implement, but very slow, and not stable.
Merge sort is very fast and stable, but requires a larger amount of temp space and arrays from recursive calls.

rickbacci

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: Respond to this question in your fork: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded). Respond below with your thoughts. Did any of the responsibilities that she lists surprise you? Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

Looking at the 4 responsibilites makes me think of MVC. Model is 'data/server communication', View is 'presentation and interaction', and Controller is 'setup'. It doesn't suprise me, becuase she breaks the parts of the app into logical parts.

I don't think I mentally did this in ideabox, and my previous projects. I'm sure I broke some things into their own functions, but I didn't look at it from this point of view.

rickbacci

///// index.js

import React from 'react';
import ReactDOM from 'react-dom';
import HelloWorld from './HelloWorld';

ReactDOM.render(<HelloWorld name='Meeka' />, document.getElementById('container')); 


///// HelloWorld.js