whostolebenfrog

(ns tron.bots
  (:require [tron.core :as tron]))

(defn up [[x y]]
  [x (dec y)])

(defn down [[x y]]
  [x (inc y)])

(defn left [[x y]]

whostolebenfrog

;; the backup bot where my real one failed
;; function name is ben

(ns tron.bots
  (:require [tron.core :as tron]))

(defn up [[x y]]
  [x (dec y)])

(defn down [[x y]]

whostolebenfrog

;; Clojure 1.5.1
=> 1
1
=> (require '[clojure.core.reducers :as r])
nil
=> (use 'clojure.repl)
nil
=> (doc r/fold)
-------------------------
clojure.core.reducers/fold

whostolebenfrog

Keybase proof

I hereby claim:

• I am whostolebenfrog on github.
• I am wsbfg (https://keybase.io/wsbfg) on keybase.
• I have a public key whose fingerprint is CDB6 CF2C 2EF6 2F0D 3B1F 76F5 BE5B 56E5 ADC0 B0F7

To claim this, I am signing this object:

whostolebenfrog

Clojure GUIs with FlatGUI

Problems with traditional approach.
- incidental complexity
- testing difficult

Looking for another way
- framework
- only need to concentrate on the app logic
- logic in one place

whostolebenfrog

Clojure and molecular serotyping of infectious disease

@rsslldnphy

Stuart Sierra's component library - lots of people doing these days?

Args being passed into functions that don't really need them, just for routing the args to the right place.
-- pushed the code from high level functions back up to the top level. not abstracting! interesting

Decided not to use protocols

whostolebenfrog

Clojure lazy + side-effects is a little odd

Resources
- file handlers
- db stuff

This is where the problem exists in clojure as these parts aren't fun.

Short lived handles;

whostolebenfrog

Automation, animation, art and dance

Generative visuals

Twissle - parameter automation library, gets params at values for the right time, smooths between two values basically.
- start with a state
- locate / sample the sequence at a time
- actually an interesting programming approach, wonder if it's worth thinking about more problems in this way (sequencing a series over the time and sampling)

tween.clj - just the tweening functions.

whostolebenfrog

Wished he had been able to go with Transient-First data structures, but they don't feel like that from a user point of view.

The whole point of transient is to take data structures and to make them go fast.

Ephemeral is take persistent structures, do interesting things to them.

Maybe persistent-first data structures!

Basic concepts;
- transients

whostolebenfrog

{
  Push {
    commits {
      sha
      message
      author {
        name
      }
      image {
        imageName