StevenBlack

Standups: 
2-3 times per night 
post issues to Slack
designate scrum master and rotate who the master will be
scrum master gives everyone a turn to speak

Conflicts: 
Write down your conflict
Spend 15 minutes tops to resolve the conflict and move on.
We are all on the same team with the same goal

StevenBlack

• This phone had its original cracked screen replaced at an iService frachise.
• The current screen worked for awhile, then gradually failed
• The current screen doesn't work at all, and the phone is disabled.

Please replace the screen, then ship to the address on the work order.

StevenBlack

// Node.js CheatSheet.
// Download the Node.js source code or a pre-built installer for your platform, and start developing today.
// Download: http://nodejs.org/download/
// More: http://nodejs.org/api/all.html


// 0. Synopsis.
// http://nodejs.org/api/synopsis.html

StevenBlack

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

StevenBlack

CREATE EXTENSION tablefunc;

CREATE TABLE sales(year int, month int, qty int);
INSERT INTO sales VALUES(2007, 1, 1000);
INSERT INTO sales VALUES(2007, 2, 1500);
INSERT INTO sales VALUES(2007, 7, 500);
INSERT INTO sales VALUES(2007, 11, 1500);
INSERT INTO sales VALUES(2007, 12, 2000);
INSERT INTO sales VALUES(2008, 1, 1000);
INSERT INTO sales VALUES(2009, 5, 2500);

StevenBlack

I have a suggestion for the Github UI in Issues.

Currently in Issues: one types Issue #17 or just #17 and this resolves to a link of the Issue. This is great!

Cool suggestion: Use of the existing Issue mini icon so the link rendering looks like this, where the current state of the issue is displayed.

Bonus Points: Hovering on the Issue link displays the Issue title in a tooltip.

StevenBlack

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 = git@github.com: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:

StevenBlack

class AbstractHook
  @oHook =  nil

  def sethook( *args )
    args.each { |arg| 
      if @hook.nil?
        @hook = arg
      else
        @hook.sethook( arg )
      end

StevenBlack

#!/bin/sh

# Source: https://www.dropbox.com/en/help/72

# Terminate Dropbox, then...

sudo chflags -R nouchg ~/Dropbox ~/.dropbox ~/.dropbox-master
sudo chown "$USER" "$HOME"
sudo chown -R "$USER" ~/Dropbox ~/.dropbox ~/.dropbox-master
sudo chmod -RN ~/.dropbox ~/Dropbox ~/.dropbox-master

StevenBlack

<!-- partial.html -->
<div class="Tile">
    {% if include.title %}
        <h1>{{ include.title }}</h1>
        {% else %}
        <h1>no content!</h1>
    {% endif %}
</div><!-- .Tile -->

<!-- in any template, partial, layout or content file -->