David Overcash funnylookinhat

Slimdown

This project has moved to github.com/jbroadway/slimdown

A very basic regex-based Markdown parser. Supports the following elements (and can be extended via Slimdown::add_rule()):

Headers
Links
Bold

Sublime Text 3 Setup

Install Package Control

Install Package Control for easy package management.

Open the console with Ctrl+`
Paste in the following:

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:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

Two developers working on independent features must never be blocked by each other
- No code freeze! Ever! For any reason!
A developer must be able to base derivative work on another developer's work, without waiting for any third party
Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
Developers must be able to work on multiple features simultaneously, or at lea

	#!/bin/bash

	function generate_ssl_cert {
	cert_name=$1

	(
	openssl genrsa -des3 -out ${cert_name}.key 1024
	openssl rsa -in ${cert_name}.key -out ${cert_name}.pem
	openssl req -new -key ${cert_name}.pem -out ${cert_name}.csr
	openssl x509 -req -days 365 -in ${cert_name}.csr -signkey ${cert_name}.pem -out ${cert_name}.crt

	// object with shader paths (optinally nested, for better structure)
	// the paths get replaced with the actual file content.
	var shaders = {
	atmoVert: 'glsl/atmo.vert.c',
	car: {
	vert: 'glsl/car.vert.c',
	frag: 'glsl/car.frag.c'
	}
	};

	<?php

	/**
	* This script is designed as a simple tool to run comparisons between varying
	* cipher suite lists used by PHP 5.5, cURL and Mozilla. The ciphersuites are
	* are hardcoded and date to 01 February 2014
	*
	* The differences are restrictions, e.g. Mozilla diff from DEFAULT shows ciphers
	* Mozilla has removed, etc. The differences should all be SSLv3 related.
	*/

	package main

	import (
	"fmt"
	"labix.org/v2/mgo"
	"labix.org/v2/mgo/bson"
	"log"
	"os"
	"strings"
	"text/tabwriter"

	{
	"directory": "bower_components"
	}