Having trouble getting packages installed in NPM? Getting an error that looks like this?? ~ npm install -g nodemon npm ERR! Darwin 13.4.0 npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "nodemon" npm ERR! node v0.10.32 npm ERR! npm v2.0.0 npm ERR! path /Users/me/.nvm/v0.10.32/lib/node_modules/nodemon/node_modules/update-notifier/node_modules/configstore/node_modules/mkdirp/package.json npm ERR! code ENOENT npm ERR! errno 34 npm …
- NPM and Nodemon install errors

Introduction When working with Git, and software in general, the most important thing for me is that the act of using the application blends seamlessly into my workflow. It should feel natural, simple, and shouldn't slow you down. I've worked with Git for a few years now, and like all things, I've kept track of my favorite tweaks and configurations. I'd like to share a few of the most awesome Git shortcuts I use on a daily basis. Configuration First …
- Awesome Git Configuration, Shortcuts, and Aliases

Here's a quick helpful template that we've refined through our work at Boombotix and OneLogin: a short pull-request template that can be used to inform team members of the status and scope of a particular feature branch. Click here for the template Preview …
- Github Pull Request Template for Gitflow

I recently came across a function declaration with a Javascript syntax that I had never seen before. !function() { // some logic } This ! bang is called the unary operator. I immediately started playing around in the Node console to try and understand this syntax. Without the bang, this function declaration will actually throw an error: function() { // nothing here } // => SyntaxError: Unexpected token ( Weird right? The reason for this is that the function defined with the ! converts what would normally be a function …
- Bangs (exclamation points) in front of function definitions in Javascript?

In a recent set of Rails services I built, my team wanted to quickly deploy to Heroku for testing. We also keep a YARD documentation server running and up to date for every deploy. Turn out there is not a simple way to do this on Heroku, as you can only run one public-facing HTTP server per application. My solution was to create a second heroku application cd /path/to/your/repo heroku create repo-name-doc git add remote docs git …
- Deploy Yard documentation server to Heroku