Nate Smith nwjsmith

Deconstruct 2017 Bibliography

Here are all of the resources mentioned by Deconstruct 2017 speakers, along with who recommended what. Please post a comment if I missed something or have an error!

DC 2017 Speakers' Choice Gold Medalist

Seeing Like a State by James Scott

Books

Public Opinion by Walter Lippmann (Evan Czaplicki)
A Pattern Language by Christopher Alexander (Brian Marick)
Domain Driven Design by Eric Evans (Brian Marick)

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

The link in the table of content jumps at the copy of the answer on this page.
The link on the answer itself points back at the original post.

Table of Content

This is a copy/paste from an internal wiki on how we should use docker

This guide is to serve as an outline of internal best practices to using Docker. The idea is to give enough information to allow engineers to create containers for new stack components while minimizing the cleanup required to make them production ready.

Concepts

Before we get to the practices, it's important to understand WHY we are doing this. The key concepts we're concerned about with broad Docker usage are provenance, determinism, repeatability and auditability.

Provenance

Provenance refers to knowing WHERE something comes from. Generally with the end use of software, this is easy:

Maven artifacts are pulled from central

	;;; `filter' MAY introduce chunkedness, therefore should only be used with
	;;; pure functions.


	(defn integers-from [n]
	(lazy-seq (cons n (do (print \.) (integers-from (inc n))))))
	;;; ⇒ #'user/integers-from

	(defn chunked-test [xs]
	(let [times-called (atom 0)

	(ns maps.core)

	;; In Clojure you can fetch items from a map three different ways. Which should
	;; you use when?

	(= "bar" ({:foo "bar"} :foo)) ; map as function
	(= "bar" (:foo {:foo "bar"})) ; key as function
	(= "bar" (get {:foo "bar"} :foo)) ; `get` as function

	;; <INCIDENTALLY>

	Generativity Thought Experiment

	Suppose I want to generate something, maybe:
	- a number
	- a string
	- a list of numbers
	- a set of parameters that define a 3d model
	- a game level
	- a poem
	- a story

	;;
	;; Example usages at the bottom of the file
	;;

	(defn productions
	"Returns a sequence of values by repeatedly calling `produce!` until it
	returns `fin`. The sequence can be used lazily/caching or reducible/non-caching.

	The arity-2 variant's `produce!` takes no arguments and returns a value
	or the terminator.

	;; warm up: balancing
	=> (s/def ::balanced
	(s/* (s/cat :open #{'<} :children ::balanced :close #{'>})))
	:user/balanced
	=> (s/conform ::balanced '[< < > < > > < >])
	[{:open <, :children [{:open <, :close >} {:open <, :close >}], :close >} {:open <, :close >}]
	=> (s/conform ::balanced '[< < > < < > > > < >])
	[{:open <, :children [{:open <, :close >} {:open <, :children [{:open <, :close >}], :close >}], :close >} {:open <, :close >}]

	;; infix to prefix

	(ns om.next.spec
	(:require [cljs.spec :as s]))

	(s/def ::ident (s/and vector? (s/cat :ident keyword? :value #(not (coll? %)))))
	(s/def ::join-key (s/or :prop keyword? :ident ::ident))
	(s/def ::join (s/and (s/map-of ::join-key ::query) #(= (count %) 1)))
	(s/def ::union (s/and (s/map-of keyword? ::query) #(> (count %) 1)))

	(s/def ::param-expr
	(s/cat :query-expr ::query-expr

	# Checklist for Weekly Review

	## Sweep

	[ ] Process work email inbox
	[ ] Process personal email inbox
	[ ] Review calendar, +/- 2 weeks.
	[ ] Review [this trigger list](http://gettingthingsdone.com/wp-content/uploads/2014/10/Mind_Sweep_Trigger_List.pdf)

	## Process