Arty Shanko obiwankenoobi

Using the “displacement by noise” method from the Mathematica StackExchange discussion, but with SVG filters.

The filter unfortunately operates pixel-by-pixel. I tried changing the filterRes parameter, but it slowed things down badly.

Tested in Chrome 23 on Ubuntu Precise, and Chrome 22 on Mac OS 10.8.

Check out Dan Foreman-Mackey's more sophisticated version of xkcd-style graphs with d3.

Discuss this on Hacker News, Reddit, or Google+.

Heroku + Github + Sensitive Data

Scenario: You deployed a Heroku project that contains sensitive data (password, API key, etc) but you want to share it on Github.

Problem: You need to commit all files necessary for the application to run on Heroku. However, pushing this to Github would reveal the sensitive info.

Solution: Have a production branch (for this example, master will be the production branch) and a Github branch. The latter contains a different .gitignore that ignores the sensitive files.

Default

Powerlevel10k

Git Submodules basic explanation

Why submodules?

In Git you can add a submodule to a repository. This is basically a repository embedded in your main repository. This can be very useful. A couple of usecases of submodules:

Separate big codebases into multiple repositories.

To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule

	var cluster = require('cluster');

	if (cluster.isWorker) {

	console.log('Worker ' + process.pid + ' has started.');

	// Send message to master process.
	process.send({msgFromWorker: 'This is from worker ' + process.pid + '.'})

	// Receive messages from the master process.

	/**
	* Module dependencies
	*/

	var express = require('express');
	var fs = require('fs');
	var mongoose = require('mongoose');
	var Schema = mongoose.Schema;

	// img path

	var app = require('express')();
	var GridStore = require('mongodb').GridStore;
	var ObjectID = require('mongodb').ObjectID;
	var MongoClient = require('mongodb').MongoClient;
	var Server = require('mongodb').Server;

	var dbConnection;
	MongoClient.connect("mongodb://localhost:27017/ersatz?auto_reconnect", {journal: true}, function(err, db) {
	dbConnection = db;
	app.listen(3000);

	// # Mocha Guide to Testing
	// Objective is to explain describe(), it(), and before()/etc hooks

	// 1. `describe()` is merely for grouping, which you can nest as deep
	// 2. `it()` is a test case
	// 3. `before()`, `beforeEach()`, `after()`, `afterEach()` are hooks to run
	// before/after first/each it() or describe().
	//
	// Which means, `before()` is run before first it()/describe()

	#!/bin/sh
	git --no-pager log -n 20 --graph --pretty=format:'%Cred%h%Creset %an: %s - %Creset %C(yellow)%d%Creset %Cgreen(%cr)%Creset' --abbrev-commit --date=relative