alexortiz201

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

alexortiz201

const I = x => x;
const K = x => y => x;
const A = f => x => f(x);
const T = x => f => f(x);
const W = f => x => f(x)(x);
const C = f => y => x => f(x)(y);
const B = f => g => x => f(g(x));
const S = f => g => x => f(x)(g(x));
const P = f => g => x => y => f(g(x))(g(y));
const Y = f => (g => g(g))(g => f(x => g(g)(x)));

alexortiz201

let module = {
  create: function(greeting, name) {
    /**
     * Ran into issue with lexical scoping when
     * using the fat arrow. Wanted to make a note
     * here.
     **/
    const obj = {
      sayIt: function () {
        console.log(this);

alexortiz201

#Offline FE Dev Set Up

• Dash App (OSX) -> Offline Docs
• npm init -> local project
• npm install --save <WANTED-REPOS>
  • set package.json to latest version
  • npm install -> when conncted to wifi for latest
• bower install <package> -> for saving bower repos locally
• Pocket -> saving articles
• Egghead.io (Premium version)

• look for video tutorials when online && download in HD

alexortiz201

Fixing npm On Mac OS X for Homebrew Users

If you just want to fix the issue quickly, scroll down to the "solution" section below.

Explanation of the issue

If you're a Mac Homebrew user and you installed node via Homebrew, there is a major philosophical issue with the way Homebrew and NPM work together. If you install node with Homebrew and then try to do npm update npm -g, you will see an error like this:

$ npm update npm -g

alexortiz201

.hover-intent(@delay){
	transition: all .25s ease-out;    
    transition-delay:@delay;
}

alexortiz201

// NOTE: I added the .js extension to this gist so it would have syntax highlighting. This file should have NO file extension

{
    // Settings
    "passfail"      : false,  // Stop on first error.
    "maxerr"        : 100,    // Maximum error before stopping.


    // Predefined globals whom JSHint will ignore.
    "browser"       : true,   // Standard browser globals e.g. `window`, `document`.

alexortiz201

<div class="progress progress-striped active">
    <div class="progress-bar"  role="progressbar" aria-valuenow="100" aria-valuemin="0" aria-valuemax="100" style="width: 100%">
        <span class="sr-only">Loading</span>
    </div>
</div>

alexortiz201

/*

//styles
.modal-nav li { width:16.6%; float: left; cursor:pointer;padding:10px 0px; margin: 0 auto; text-align: center;}
.modal-nav li:last-child {width:17%;}

// button
<li data-state="camera"><img src="/assets/images/icons/icon-camera.png" alt="Camera" /></li>

alexortiz201

$(function () {

    var slides = [],
        liSize = $(window).width(),
        autoplay = true,
        step = 1,
        current = 0,
        maximum = 0,
        visible = 1,
        speed = 200,