brettkelly

tell application "Finder"
	try
		set appPath to (path to application "Evernote" as text)
	on error
		display dialog "Couldn't find Evernote. Is it installed?"
	end try
	set printPath to (path to "dlib" from user domain as text) & "PDF Services"
	make new alias at printPath to appPath with properties {name:"Send PDF to Evernote"}
end tell

pfreixes

# pfreixes, 2012-07-27
# Add to /etc/bash_completion.d/supervisorctl
  
_supervisor()
{
    local cur prev opts base
    COMPREPLY=()
    cur="${COMP_WORDS[COMP_CWORD]}"
    prev="${COMP_WORDS[COMP_CWORD-1]}"

rantav

A few show tricks to find slow queries in mongodb

Enable profiling

First, you have to enable profiling

> db.setProfilingLevel(1)

Now let it run for a while. It collects the slow queries ( > 100ms) into a capped collections, so queries go in and if it's full, old queries go out, so don't be surprised that it's a moving target...

kyleve

/**
 Provides the ability to verify key paths at compile time.
 
 If "keyPath" does not exist, a compile-time error will be generated.
 
 Example:
    // Verifies "isFinished" exists on "operation".
    NSString *key = SQKeyPath(operation, isFinished);
 
    // Verifies "isFinished" exists on self.

jkottke

Not sure how to summarize/organize this into something useful. Some can be made into Spotify/Rdio playlists, but others are likely unavailable and some are just URLs to other services. Genre is all over the place as well...lots of ambient and classical, soundtracks, uptempo dancey stuff, rock w/ words, and even Slayer. Not sure all that can be put into one playlist that's useful for anyone. What I'm saying is, good luck!

 fantoraygun ‏@fantoraygun  1h
@jkottke some great mixes here: http://musicforprogramming.net/ 

 Andrew ‏@jandrewc  1h
@jkottke "From here we go sublime" by The Field and "Alive 2007" by Daft Punk.

 Lenny ‏@lenny_  1h
@jkottke SomaFM's Groove Salad station

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

alangpierce

Snapshot of Khan Academy's BigBingo A/B testing framework and related code.

Here's a basic overview:
-summarize.py is the most interesting file. It contains all stages of the
summarize task, as well as the publish and archive steps that happen at the
end.
-bq_pipelines.py contains lots of useful pipelines for interacting with
BigQuery. QueryToTableBatchPipeline can run many simultaneous queries, and will
properly handle all batching and retry logic.
-config.py is where all experiment configuraiton lives. For this Gist, I

vasco3

Table of Contents generated with DocToc

• FrontEnd Masters - ES6 notes
  • Proper Tail Call (PTC)
  • Function Hoisting
  • Variables
    • Temporal Dead Zone
• Rest Parameters

dgraham

(function() {
  function createNode(text) {
    var node = document.createElement('pre');
    node.style.width = '1px';
    node.style.height = '1px';
    node.style.position = 'fixed';
    node.style.top = '5px';
    node.textContent = text;
    return node;
  }

q42jaap

import Layer from 'express/lib/router/layer';
const Promise = global.Promise;

/**
 * "fixt" express mbt promises. Als een stukje middleware een promise returnt dan moeten errors eigenlijk aan next worden gegeven.
 *
 * We hadden ook de suffix `Async` kunnen gebruiken om naast de bestaande functies nieuwe te maken. Dat heeft een flink nadeel
 * omdat de api op verschillende manieren te benaderen is.
 */