Jorin jorinvo

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
Atomic/related changes all in one commit is something worth striving for. Having your dev

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

fireplace

cpr => (require ... :reload)
cpR => (require ... :reload-all)

Evaluation

:Eval (clojure code) => runs (clojure code) in repl
cpp => evaluate inn-most expessions under cursor
cp<movement> => evaluate text described by <movement>
cqp => opens quasi-repl
cqc => quasi-repl command line window

	var last = function(fn, l) {
	return function() {
	var args = Array.prototype.slice.call(arguments);
	args.push(l);
	return l = fn.apply(null, args);
	};
	};

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="UTF-8">
	<title>Demo for Basic Image Filtering Using a Canvas Element</title>
	</head>
	<body>

	<div>
	<input type="file" id="loader">

	#!/usr/bin/env bash

	# Check that terminfo exists before changing TERM var to xterm-256color
	# Prevents prompt flashing in Mac OS X 10.6 Terminal.app
	if [ -e /usr/share/terminfo/x/xterm-256color ]; then
	export TERM='xterm-256color'
	fi

	# Turn off standout; turn off underline
	tput sgr 0 0

	App configuration in environment variables: for and against

	For (some of these as per the 12 factor principles)

	1) they are are easy to change between deploys without changing any code

	2) unlike config files, there is little chance of them being checked
	into the code repo accidentally

	3) unlike custom config files, or other config mechanisms such as Java

	(function($){

	/* addClass shim
	****************************************************/
	var addClass = $.fn.addClass;
	$.fn.addClass = function(value) {
	var orig = addClass.apply(this, arguments);

	var elem,
	i = 0,

	#!/bin/bash

	# Usage: slackpost <token> <channel> <message>

	# Enter the name of your slack host here - the thing that appears in your URL:
	# https://slackhost.slack.com/
	slackhost=PUT_YOUR_HOST_HERE

	token=$1

	/*
	In the node.js intro tutorial (http://nodejs.org/), they show a basic tcp
	server, but for some reason omit a client connecting to it. I added an
	example at the bottom.

	Save the following server in example.js:
	*/

	var net = require('net');