martindale

const I = x => x;
const K = x => y => x;
const A = f => x => f(x);
const T = x => f => f(x);
const W = f => x => f(x)(x);
const C = f => y => x => f(x)(y);
const B = f => g => x => f(g(x));
const S = f => g => x => f(x)(g(x));
const P = f => g => x => y => f(g(x))(g(y));
const Y = f => (g => g(g))(g => f(x => g(g)(x)));

martindale

<?php
  function insertParsedMessageRoll($textParts) {
		if(count($textParts) == 1) {
			// default is one d6:
			$text = '/roll '.$this->getUserName().' 1d6 '.$this->rollDice(6);
		} else {
			$diceParts = explode('d', $textParts[1]);
			if(count($diceParts) == 2) {
				//Number of times to roll
				$number = $diceParts[0];

martindale

A lot of people on Reddit think of Bitcoin primarily as a competitor to card payment networks. I think this is more than a little odd-- Bitcoin is a digital currency. Visa and the US dollar are not usually considered competitors, Mastercard and gold coins are not usually considered competitors. Bitcoin isn't a front end for something that provides credit, etc.

Never the less, some are mostly interested in Bitcoin for payments (not a new phenomenon)-- and are not so concerned about what are, in my view, Bitcoin's primary distinguishing values-- monetary sovereignty, censorship resistance, trust cost minimization, international accessibility/borderless operation, etc. (Or other areas we need to improve, like personal and commercial privacy) Instead some are very concerned about Bitcoin's competitive properties compared to legacy payment networks. ... And although consumer payments are only one small part of whole global space of money, ... mon

martindale

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1

mQINBFf9GRcBEACw7pwmSz59OT/IxD3MJP7UZSzz7ZjJrqWEEiYufl1R5wTlCkzO
ZAehjU7g0li+kpSW67LLgIHy9ZGGiL0Rm6wJ006faTklpmxVfU2uLAG3LzmEqyoa
2Tsh+wTMT8Tv7/owry5qtZtNSPfg4waAPYKcY6CIWQ8jDJcYlKm/yRcqjKWIEs8T
Hji95d6dQOeNPghKlYaTcJzDNJLH4XwOhYVJdP0D3HL/S8dvmy2TsdLoZ7D62inM
6EQFZ/UAvlCn6JNPmNkIRMcx5JR/42fDyoPSIYgwZYU3YwBmXGu7kVfoNX1+iJYL
oMpZw4hoMct3lAqs7Ngy81YBqjHSfPA9iVp2ihLqFV1oo8i8QqMyV6UnSxGvzDqs
1ttax0ymkiqjHgLrlzzJyFdd+XpQKrOL3CC+qPpa4/T419tJCsGoYxCDibyiNRZ8

martindale

shopt -s expand_aliases

rm -r ~/elementsdir1
rm -r ~/elementsdir2
rm -r ~/bitcoindir
mkdir ~/elementsdir1
mkdir ~/elementsdir2
mkdir ~/bitcoindir

martindale

Keybase proof

I hereby claim:

• I am martindale on github.
• I am martindale (https://keybase.io/martindale) on keybase.
• I have a public key ASCgK40qCoCCkyDLMT-K2427IqbHJMrew_is8IXJZVSuqwo

To claim this, I am signing this object:

martindale

alias accio=wget
alias avadaKedavra='rm -f'
alias imperio=sudo
alias priorIncantato='echo `history |tail -n2 |head -n1` | sed "s/[0-9]* //"'
alias stupefy='sleep 5'
alias wingardiumLeviosa=mv

alias sonorus='set -v'
alias quietus='set +v'

martindale

While the standard 80 character limit for source code can be traced back to the
IBM punch card[1] it can still be seen as a good upper bound for how long lines
of text should be on modern high definition displays.

First thing we must acknowledge is that source code is not read in the
traditional sense. Instead developers scan the source using non-linear eye
movements[2] or stay fixated in a small area of code while working out the
logical details of code being written. The fixation on a single location, even
for more than a few seconds, leads to a loss of visual accuity. Which occurs
when the eyes do not perform frequent saccadic eye movements.[3] Further

martindale

Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.

By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.

martindale

curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}'