Gerardo Bort gerardobort

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

How to use Tim Pope’s Pathogen

I’ll assume you are on Linux or Mac OSX. For Windows, replace ~/.vim/ with $HOME\vimfiles\ and forward slashes with backward slashes.

The idea

Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your ~/.vim/ directory. Syntax scripts go into ~/.vim/syntax/, plugin scripts go into ~/.vim/plugin, documentation goes into ~/.vim/doc/ and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.

This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under ~/.vim/bundle/, where each directory simulates the standard structure of your ~/.vim/ directory.

Getting SimpleOpenNI working in Processing on Ubuntu 13.10

There's still obviously not a great, reliable installation path for SimpleOpenNI. But this is what worked for me (it got me to the point of the DepthImage example sketch working).

I visited the simple-openni installation page and followed its extra Linux instructions:

cd ~/Downloads
wget https://simple-openni.googlecode.com/svn/trunk/SimpleOpenNI-2.0/platform/linux/installLinuxRules.sh
wget https://simple-openni.googlecode.com/svn/trunk/SimpleOpenNI-2.0/platform/linux/primesense-usb.rules

	Mute these words in your settings here: https://twitter.com/settings/muted_keywords

	ActivityTweet
	generic_activity_highlights
	generic_activity_momentsbreaking
	RankedOrganicTweet
	suggest_activity
	suggest_activity_feed
	suggest_activity_highlights
	suggest_activity_tweet

	#!/bin/env node
	//thx to http://fsprojects.github.io/Chessie/a-tale-of-3-nightclubs.html

	Promise.all([
	suitablePersonEnterGayBar(),
	unsuitablePersonEnterGayBar(),
	])
	.then(result => result.map((person, i) => `Person ${i+1}: ${person.cost \|\| ''}${person.reasons.join(' ')}`))
	.then(result => console.log(`Person entries\n${result.join('\n')}`));

	/* Useful celery config.

	app = Celery('tasks',
	broker='redis://localhost:6379',
	backend='redis://localhost:6379')

	app.conf.update(
	CELERY_TASK_RESULT_EXPIRES=3600,
	CELERY_QUEUES=(
	Queue('default', routing_key='tasks.#'),

	web: run-program gunicorn arena.wsgi

	celery_beat: run-program celery -A arena beat -l info

	celery1: run-program celery -A arena worker -Q default -l info --purge -n default_worker

	celery2: run-program celery -A arena worker -Q feeds -l info --purge -n feeds_worker

	= Why JIRA should use Neo4j

	== Introduction

	There are few developers in the world that have never used an issue tracker. But there are even fewer developers who have ever used an issue tracker which uses a graph database. This is a shame because issue tracking really maps much better onto a graph database, than it does onto a relational database. Proof of that is the https://developer.atlassian.com/download/attachments/4227160/JIRA61_db_schema.pdf?api=v2[JIRA database schema].

	Now obviously, the example below does not have all of the features that a tool like JIRA provides. But it is only a proof of concept, you could map every feature of JIRA into a Neo4J database. What I've done below, is take out some of the core functionalities and implement those.

	== The data set

	<?php
	class ReconnectingPDO
	{
	protected $dsn, $username, $password, $pdo, $driver_options;

	public function __construct($dsn, $username = "", $password = "", $driver_options = array())
	{
	$this->dsn = $dsn;
	$this->username = $username;
	$this->password = $password;