mtnygard

(require [clojure.test.check.generators :as gen])

(defn ptable
  [label cols & rows]
  (let [ncols (count cols)]
    (assert (= 0 (mod (count rows) (inc ncols))))
    (mapcat
     (fn [[r & vs]]
       (map (fn [c v] [v [c r]]) cols vs))
     (partition (inc ncols) rows))))

mtnygard

(ns support.service
  (:require [io.pedestal.http :as http]
            [io.pedestal.http.route :as route]))

(defn about-page
  [request]
  {:status 200 :body (format "Clojure %s - served from %s"
                              (clojure-version)
                              (route/url-for ::about-page))})

mtnygard

Keybase proof

I hereby claim:

• I am mtnygard on github.
• I am mtnygard (https://keybase.io/mtnygard) on keybase.
• I have a public key ASBwxeoj-3gX6AwhrGHus60trRH4_ZYUdh-up2NGqCu46Qo

To claim this, I am signing this object:

mtnygard

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

mtnygard

;; Let's start with a simple conditional interceptor that works with functions...

(defn conditional-context                                                                                       
  "Given a keyword name and any variable predicate and terminator function pairs,                               
  return an interceptor that will apply the terminator function paired to the first                             
  truthy predicate.  Predicates and terminators are both given the context as                                   
  the only argument.                                                                                            
  If all predicates fail, the original context is returned."                                                    
  [name-kw & pred-terms]                                                                                        

mtnygard

Verifying that +mtnygard is my blockchain ID. https://onename.com/mtnygard

mtnygard

- Information and the Nature of Reality, Davies and Gregersen
- Swarm Intelligence, Bonabeau, Dorigo, Theraulaz
- Chaos, ed. Arun V. Holden
- Linked, Baraboa
- The Origins of Order, Kauffman
- Investigations, Kauffman
- Emergence, Steven Johnson
- Elements of Information Theory, Cover, Thomas
- The End of Certainty, Prigogine
- Physical Fluid Dynamics, Tritton

mtnygard

Sequence	Action
ad	add declaration for current top-level form
ai	add import to namespace declaration, then jump back
ap	add a dependency to your project depends on refactor-nrepl
ar	add require to namespace declaration, then jump back (see optional setup)
au	add "use" (ie require refer all) to namespace declaration, then jump back
cc	cycle surrounding collection type
ci	refactoring between if and if-not
cp	cycle privacy of defns and defs

mtnygard

"... the Tracy-Widom distribution and its large deviation tails represent a universal phase transition between weak- and strong-coupling phases."

http://www.simonsfoundation.org/quanta/20141015-at-the-far-ends-of-a-new-universal-law/

mtnygard

Reciprocal Needs in the Employment Relation

We can look at two sides of the management coin: What do the individuals get out of it? And what benefit does the whole system derive from it?

I will disregard any benefits that accrue to managers just by holding the position of managing. Those are just circular logic. Circular logic abounds in discussions of management and hierarchy. For example, consider status reports. It will be said that status reports are necessary so managers know what their employees are working on. It’s