Aaron Buchanan aaronbuchanan

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

## index.html
<div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
      <div class="container-fluid">
        <div class="navbar-header">
          <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
            <span class="sr-only">Toggle navigation</span>
            <span class="icon-bar"></span>
            <span class="icon-bar"></span>
            <span class="icon-bar"></span>
          </button>
          <a class="navbar-brand" href="#">Project Name</a>

## rename_files_with_prefix.sh
$ for filename in OrigPrefix*; do echo mv \"$f\" \"${f//OrigPrefix/NewPrefix}\"; done

## persistent_ulimit.sh
launchctl limit maxfiles 2048 2048 && ulimit -n 2048

## gist:2dcf936daceab925da61
Purpose Outcome Structure Timing
Having a plan for sales meetings, before the actual meeting will improve your chances of success.

Winging it is not a good strategy. You really need to think in advance what is the Purpose of the meeting and what is the Outcome of the meeting.  You want the Purchase Order (PO) so think about the Purpose and the Outcome.

Be realistic about what can be achieved in the meeting.  Ideally think about what  the customer wants from the meeting - not just what you want. If you draw an analogy with dating - you might want sex on the first date but is it realistic?  Having a clear view on small incremental steps forward towards the end goal is important otherwise you can end up in a protracted Engagement and never get Married (get the sale) or worse still turn the sale off by being too pushy!

Using the POST (Purpose Outcome Structure Timing) tool will help you have more effective sales meetings.
Purpose - what is the reason for the meeting.  If it's a first meeting the purpose might

## gist:4e378ff5e96cb2cb28bf
$ gource -f -1280x720 --auto-skip-seconds 1 --bloom-multiplier 1.0 --bloom-intensity 1.2 -e 0.2 --background 000000 --background-image gource/bg.png --seconds-per-day .2 --highlight-all-users -o gource/out.ppm
$ ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i gource/out.ppm -vcodec libx264 -preset ultrafast -pix_fmt yuv420p -crf 1 -threads 0 -bf 0 gource/out.mp4

## gist:5df6887f76026bb25acb
@implementation InterfaceController
{
    SRWebSocket *_webSocket;
}

- (void)awakeWithContext:(id)context {
    [super awakeWithContext:context];
}

- (IBAction)didOpen {

## gist:353f10ddcb0d4a175661
<smil><head><layout><root-layout width="2460px" height="1440px"/><region id="Image" left="0" top="0" width="2460px" height="1296px" fit="meet"/></layout></head><body><par dur="5000ms"><img src="20150815_140057.jpeg" region="Image"/></par></body></smil>

## top 100 domain occurrences by email.sql
select count(*) as occurrances, substring_index(email, "@", -1) as domain
from users
group by substring_index(email, "@", -1)
ORDER by occurrances DESC
limit 100;

## Gulpfile.js
var gulp = require('gulp');
var source = require('vinyl-source-stream');
var request = require('request');
var merge = require('merge2');
var concat = require('gulp-concat');
var buffer = require('gulp-buffer');

/**
 * 1. We request the latest jQuery version from the jQuery CDN. The
 *    request package allows for streaming. What we get in return
	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	<div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
	<div class="container-fluid">
	<div class="navbar-header">
	<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
	<span class="sr-only">Toggle navigation</span>
	<span class="icon-bar"></span>
	<span class="icon-bar"></span>
	<span class="icon-bar"></span>
	</button>
	<a class="navbar-brand" href="#">Project Name</a>
	Purpose Outcome Structure Timing
	Having a plan for sales meetings, before the actual meeting will improve your chances of success.

	Winging it is not a good strategy. You really need to think in advance what is the Purpose of the meeting and what is the Outcome of the meeting. You want the Purchase Order (PO) so think about the Purpose and the Outcome.

	Be realistic about what can be achieved in the meeting. Ideally think about what the customer wants from the meeting - not just what you want. If you draw an analogy with dating - you might want sex on the first date but is it realistic? Having a clear view on small incremental steps forward towards the end goal is important otherwise you can end up in a protracted Engagement and never get Married (get the sale) or worse still turn the sale off by being too pushy!

	Using the POST (Purpose Outcome Structure Timing) tool will help you have more effective sales meetings.
	Purpose - what is the reason for the meeting. If it's a first meeting the purpose might
	$ gource -f -1280x720 --auto-skip-seconds 1 --bloom-multiplier 1.0 --bloom-intensity 1.2 -e 0.2 --background 000000 --background-image gource/bg.png --seconds-per-day .2 --highlight-all-users -o gource/out.ppm
	$ ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i gource/out.ppm -vcodec libx264 -preset ultrafast -pix_fmt yuv420p -crf 1 -threads 0 -bf 0 gource/out.mp4
	@implementation InterfaceController
	{
	SRWebSocket *_webSocket;
	}

	- (void)awakeWithContext:(id)context {
	[super awakeWithContext:context];
	}

	- (IBAction)didOpen {
	select count(*) as occurrances, substring_index(email, "@", -1) as domain
	from users
	group by substring_index(email, "@", -1)
	ORDER by occurrances DESC
	limit 100;
	var gulp = require('gulp');
	var source = require('vinyl-source-stream');
	var request = require('request');
	var merge = require('merge2');
	var concat = require('gulp-concat');
	var buffer = require('gulp-buffer');

	/**
	* 1. We request the latest jQuery version from the jQuery CDN. The
	* request package allows for streaming. What we get in return