Aaron Buchanan aaronbuchanan

## 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>

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

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

- (IBAction)didOpen {

## 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: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

## 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

## 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>

## 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

## screenshots.js
/*
* Takes provided URL passed as argument and make screenshots of this page with several viewport sizes.
* These viewport sizes are arbitrary, taken from iPhone & iPad specs, modify the array as needed
*
* Usage:
* $ casperjs screenshots.js http://example.com
*/

var casper = require("casper").create();

## brew-services.rb
#!/usr/bin/env ruby -w

# brew-services(1) - Easily start and stop formulas via launchctl
# ===============================================================
#
# ## SYNOPSIS
#
# [<sudo>] `brew services` `list`<br>
# [<sudo>] `brew services` `restart` <formula><br>
# [<sudo>] `brew services` `start` <formula> [<plist>]<br>
	@implementation InterfaceController
	{
	SRWebSocket *_webSocket;
	}

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

	- (IBAction)didOpen {
	$ 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
	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
	<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>
	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	/*
	* Takes provided URL passed as argument and make screenshots of this page with several viewport sizes.
	* These viewport sizes are arbitrary, taken from iPhone & iPad specs, modify the array as needed
	*
	* Usage:
	* $ casperjs screenshots.js http://example.com
	*/

	var casper = require("casper").create();
	#!/usr/bin/env ruby -w

	# brew-services(1) - Easily start and stop formulas via launchctl
	# ===============================================================
	#
	# ## SYNOPSIS
	#
	# [<sudo>] `brew services` `list`<br>
	# [<sudo>] `brew services` `restart` <formula><br>
	# [<sudo>] `brew services` `start` <formula> [<plist>]<br>