simpsoka

Do I want to die on this hill?

• Pass: This is morally good and if not handled has long term consequences
• Fail: This if self serving

Am I including everyone?

• Pass: My ego is not driving this conversation
• Fail: The people in this conversation will only tell me I'm right and not push back

aakropotkin

#! /usr/bin/env bash

# Provided a list of package and option names (provided by my `writeOpts.sh` and 
# `writePacks.sh` scripts), fuzzy search package and options information.
# The selection's definition will be opened in vim (as readonly) for viewing.
# NOTE: This script opens the result in a new URxvt window, you most likely will want
#       to change that to open in the current window, or your own Terminal Emulator of
#       choice. The current implementation is intended for use with a temporary XMonad
#       scratchpad, which dies immediately after exiting (thus a new URxvt window is
#       required).

tpolecat

Hi, looking for scalac flags?

This gist has been upgraded to a blog post here.

gvn

Eliminating Code Smell With Grunt

by Gavin Lazar Suntop @gvn

Intro

I love clean code. There, I said it. I pride myself on passing strict linting standards and keeping my code easy to read. It's not just a personal proclivity, but a choice I hope benefits other developers.

My general experience with teams has been that code style is something people care about and have strong personal preferences. Typically, at some point people get tired of dealing with inconsistency and a standardization meeting is called. This is, of course, an important discussion to have. The problem that tends to occur is either lack of documentation or lack of enforcement of the agreed upon style. Additionally, new team members or contributors may not have access to a clear set of rules.

goldhand

1. Set keyboard discoverable
2. Get the mac address of the bluetooth device:
     $ hcitool scan
3. Create new device:
     $ sudo bluez-simple-agent hci0 [bluetooth device mac address = XX:XX:XX:XX:XX:XX]
   which will hopefully return somthing like:
     DisplayPasskey (/org/bluez/537/hci0/..., [PIN = 123456])
   else:
     $ sudo bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX repair
   start over

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

angus-c

//usage
withAdvice.call(targetObject);

//mixin augments target object with around, before and after methods
//method is the base method, advice is the augmenting function
withAdvice: function() {
  ['before', 'after', 'around'].forEach(function(m) {
    this[m] = function(method, advice) {
      if (typeof this[method] == 'function') {
        return this[method] = fn[m](this[method], advice);

Shadowfiend

package bootstrap.liftweb {
  import net.liftweb.common._
  import net.liftweb.http._
    import js._
    import LiftRules._
  import net.liftweb.util.Helpers._

  /**
   * Provides automatic reloading of the client on session loss.
   *

heralight

package code.mockweb
/*
 * Copyright 2011 WorldWide Conferencing, LLC
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *

pamelafox

// Includes functions for exporting active sheet or all sheets as JSON object (also Python object syntax compatible).
// Tweak the makePrettyJSON_ function to customize what kind of JSON to export.

var FORMAT_ONELINE   = 'One-line';
var FORMAT_MULTILINE = 'Multi-line';
var FORMAT_PRETTY    = 'Pretty';

var LANGUAGE_JS      = 'JavaScript';
var LANGUAGE_PYTHON  = 'Python';