dustingetz

References — Electric Clojure

Electric Clojure implements a form of arrowized continuous time dataflow programming with extensions for network-transparent function composition.

• The Haskell School of Music: From Signals to Symphonies (2018) — best starting point and also a great intro to Haskell.
• The Essence of Dataflow Programming (2006) great category theory overview of dataflow programming; missing Applicative (2008), Free monad and Cofree comonad
• Push-pull functional reactive programming, Elliot (2009)
• Breaking down FRP, Jane Street (2014) — good concise comparision of many FRP aspects; missing discussion of discrete vs continuous
• [Compiling to Categories, Elliott (2017)](http

dustingetz

Missionary concept map

Missionary primitives fit into three categories:

Effect descriptions = pure functional programming which is about trees not graphs

• continuous flow, m/?< (switch)
• m/watch, m/latest, m/cp
• m/observe
• m/reductions, m/relieve

oliyh

(import '[java.util Timer TimerTask])

(defn debounce
  ([f] (debounce f 1000))
  ([f timeout]
    (let [timer (Timer.)
          task (atom nil)]
      (with-meta
        (fn [& args]
          (when-let [t ^TimerTask @task]

borkdude

(require '[clojure.core.match :refer [match]]
         '[clojure.string :as str]
         '[hiccup2.core :refer [html]]
         '[org.httpkit.server :as server])

(defn router [req]
  (let [paths (vec (rest (str/split (:uri req) #"/")))]
    (match [(:request-method req) paths]
           [:get ["users" id]] {:body (str (html [:div id]))}
           :else {:body (str (html [:html "Welcome!"]))})))

x3ro

#!/bin/bash

# We need the TAB character for SED (Mac OS X sed does not understand \t)
TAB="$(printf '\t')"

function abort {
    echo "$(tput setaf 1)$1$(tput sgr0)"
    exit 1
}

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real