Adrian Mowat mowat27

Notes on Playing Lean

Buy - http://www.playinglean.com/products/playing-lean-the-game

Salient Facts

You have to build a company using your limited resources. You start out with a team of 3 represented by the blue cylinders and on each turn you have to choose how best to apply them to creating your product and/or selling to customers. As your company grows, you can employ more people but your choices are still limited by its size and capability.

component/Lifecycle

System construction and desctruction only
Once your compnents have been created, they are on their own
- i.e. it does not automatically add anything to a request/opartaion

Add something to every request

Create a RingHandlerProvider designed to run just after the web server

Glasgow Clojure Dojo - 2 April 2014

Candidate Topics

A unit test generator for Clojure - aimed at legacy code
Conway's game of life
Ray casting - does a ray intersect with a polygon?

The unit test generator was almost unanimously chosen.

Hammock Driven Development

Taken from Rich Hickey's day 2 keynote at Clojure Conj 2010.

Notes

What is the problem?

What issue(s) have been reported?
What sort of abnormal behaviour have you noticed?
What error(s) are you seeing?

How does this problem affect your customers?

Many problems a team encounters will have a direct impact on how people use your sites. It is very important to understand how your work will affect your customers before you decide on a solution to the problem. If you don't, it will be tempting to write code that "fixes" the immediate issue but does not really improve the system as a whole. Instead of making the system better, you will have introduced technical debt that will be paid back in the form of unexpected problems or reduced flexibility later.

	<!DOCTYPE html>
	<meta charset="utf-8">
	<style>

	.node {
	font: 11px "Helvetica Neue", Helvetica, Arial, sans-serif;
	}

	.link {
	stroke: steelblue;

	(ns game-of-life.core)

	(def world [[2 1] [2 2] [1 1]])

	(defn neighbours [[x y]]
	[[(dec x) (dec y)] [x (dec y)] [(inc x) (dec y)]
	[(dec x) y] [(inc x) y]
	[(dec x) (inc y)] [x (inc y)] [(inc x) (inc y)]])

	(neighbours [2 2])

	refine = (x, y...) ->
	console.log "required: #{x}"
	console.log "optional: #{y.join(', ')}" if y.length > 0

	walk = (head, tail...) ->
	console.log head
	walk.apply(@, tail) if tail.length

	# Exercises
	start = (num) ->

	; We had an interesting chat about using collections
	; as functions. In summary...

	; get returns an item from a collection
	(get [:a :b :c] 1)
	:b
	(get {:a 1, :b 2} :b)
	2
	(get #{:a :b :c} :c)
	:c

	(require 'package)
	(add-to-list 'package-archives
	'("marmalade" . "http://marmalade-repo.org/packages/"))
	(package-initialize)

	(defvar my-packages '(clojure-mode
	cider
	paredit
	auto-complete
	highlight-parentheses