benmccormick

## Explanation

This was my end of 2012 software inventory.  The goal was to identify all of the things I use software for, evaluate what the best software was to use for those use cases, and then commit to using that software for all of 2013.  The goals were simplicity, productivity, and a more focused approach to the tools I use.

## Use Cases & Solutions

#### Web Browsing in Windows

* **Chrome** - I don't love Google's business model.  And their designs are hit and miss. But they really do make some great software.  In my experience Chrome is the best browser to debug with, the fastest, and handles multiple tabs & searching the best.  

benmccormick

"<Your Name Here>

" Setup stuff
" ===========

" Use vim rather than vi settings
set nocompatible


" Plugins Setup

benmccormick

" A minimal vimrc for new vim users to start with.
"
" Referenced here: http://vimuniversity.com/samples/your-first-vimrc-should-be-nearly-empty
"
" Original Author:	     Bram Moolenaar <Bram@vim.org>
" Made more minimal by:  Ben Orenstein
" Modified by :          Ben McCormick
" Last change:	         2014 June 8
"
" To use it, copy it to

benmccormick

Keybase proof

I hereby claim:

• I am benmccormick on github.
• I am ben_mccormick (https://keybase.io/ben_mccormick) on keybase.
• I have a public key ASA-PhwIqziP2g1Ycexv29-bEBSVn-qNjgtQRZ0ZLDjIbgo

To claim this, I am signing this object:

benmccormick

There are a few core concepts that are useful to understand when building Marionette applications.

Marionette is designed to help you build build scalable web applications by providing common design patterns as a series of components.Those components are implementations of the concepts described here.

Marionette's concepts build on the concepts introduced by Backbone. If you are new to Backbone, don't worry. This page

benmccormick

Marionette 3 is currently in development, but one of its main thrusts is going to be simplifying the concepts needed for Marionette Developers. This involves deprecating and renaming some features. This gist is meant to provide a mapping of V2 to V3 concepts to help developers plan for and understand v3.

Disclaimers:

• this is not an official document
• I'm not on the Mn core team, this is just the understanding of an observer of the library
• Mn V3 is still in development. I'll try to keep this document up to date, but if something looks wrong please leave a comment and double check.

Concepts table

benmccormick

module.exports = function (file, api) {
    const j = api.jscodeshift;

    const buildDecoratorPropertiesFromCurrentObject = currentObj => {

        let decoratorProps = [];
        currentObj.properties.forEach(prop => {
            if (prop.value.type === 'CallExpression' && prop.value.callee.name === 'computed') {
                prop.kind = 'get';
                let fnBody = prop.value.arguments[0];

benmccormick

bootstrap -css
tensorflow - python
react -js
vue -js
d3 - js
react-native -js
angular.js - js
animate.css - css
jquery - js
laravel - php

benmccormick

/* takes a list of params in the format
    [{
        key: 'foo'
        value: 'bar'
    }]
    or an object with key-value params
    {
        foo: 'bar'
    }
}

benmccormick

let arr = [1, 2, 3];

function log(item) {
    console.log(item);
}

//forEach performs an action on each item 
//in an array

arr.forEach(log); //logs 1 2 3 in order