Jorin jorinvo

Follow the dirty money

A shady Internet business has been discovered.

The website has been made public by a whistle blower. We have enough evidence about the dirty deals they did. But to charge them we need to get hands on precise numbers about the transactions that happened on their platform.

Unfortunately no record of the transactions could be seized so far. The only hint we have is this one transaction:

Create Root CA (Done once)

Create Root Key

Attention: this is the key used to sign the certificate requests, anyone holding this can sign certificates on your behalf. So keep it in a safe place!

openssl genrsa -des3 -out rootCA.key 4096

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

require-from-twitter

Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.

How to use

Source tweet: https://twitter.com/rauchg/status/712799807073419264

const leftPad = await requireFromTwitter('712799807073419264');

Condition Systems in an Exceptional Language by Chris Houser

I recently watched Chris Houser's talk from Clojure/conj 2015 on condition systems in Clojure. I enjoyed the subject, so I decided to write up the talk as a way of encouraging me to really understand it, and in the hope that it might help others understand it.

The last time I heard about Common Lisp's condition system was at a talk by Didier Verna at ACCU in Bristol in 2013 (slides here). It sounded really interesting, but I didn't understand it well enough.

tl;dr

Chris Houser talks about different ways of handling errors in Clojure. Based on examples from Peter Seibel's book, Practical Common Lisp, he describes condition systems, which are also known as resumable exceptions, or restarts.

	const pipeline = (...fns) => (val) => fns.reduce((prom, fn) => prom.then(fn), Promise.resolve(val));

	const myPipe = pipeline(
	(val) => val + 1,
	(val) => val + 1
	);

	Promise.resolve(1)
	.then(myPipe)
	.then((result) => {

	(ns gumball-machine.core
	(:require [thi.ng.color.core :as col]
	[thi.ng.math.core :as m]
	[thi.ng.geom.core :as g]
	[thi.ng.geom.core.vector :refer [vec3]]
	[thi.ng.geom.physics.core :as ph]
	[thi.ng.geom.sphere :refer [sphere]]
	[quil.core :as q :include-macros true]))

	(def particles

	# These examples assume you have a container currently running.

	# 1 Pipe from a file
	sudo docker exec --interactive CONTAINER_NAME /bin/bash < the_beginning.sh \| tee the_beginning_output.txt`

	#2a Pipe by piping
	echo "echo This is how we pipe to docker exec" \| sudo docker exec --interactive CONTAINER_NAME /bin/bash -

	-- paste into http://elm-lang.org/try and click "compile"
	-- http://imgur.com/gallery/W6TwgZw

	import Graphics.Collage exposing (..)
	import Graphics.Element exposing (..)
	import Text
	import Color exposing (..)
	import Time
	import Signal

	(defn get-free-port []
	(with-open [socket (ServerSocket. 0)]
	(.getLocalPort socket)))