don’t know- there’s an infinite amount of stuff you don’t know, probability of something better within that is much stronger than in the stuff you know Next slide: concrete examples from energy
these are symptoms/examples of where experimentation is difficult. next slide: what can we do to achieve more experimentation
distinct concepts: easier to manoeuvre and try out better ways of solving problem utility: focus on what’s needed, not what’s ‘real’. tube map is a good way to navigate london, terrible way to understand the geography. also ancient map that world is flat.
follows from an emphasis on model utility allows contexts to be played with individually recognise that there’s a mapping to be done, deal with it in the right place, rather than everywhere! so let’s look at our contexts...
rate cards distinct from plans + pricing, in turn distinct from dealing with customers and getting them through the switch. we’ve done bits of experimentation in all, although the pricing and comparison is where the action is so lets talk about that a bit more about one...
so energy comparison is our context. lets look at what it needs to do and look at the experimentation we did. lets take a look at the physical (and logical) app separation and our end result (so far)
pretty normal stuff- sinatra, mysql and ruby around the edges. in the middle we’re using some new stuffs. thats been beneficial (we’ll come to it in a minute), but lets take a look at some risks we considered at the outset
not sufficient to just learn during the day, needs a keen interest from people
so turns out, a lot of tools in clojure have sprung up inspired from ruby counterparts. and, our experience of ruby deploys meant clojure deploys were little effort.
Comparison took 3 weeks to write in Clojure
2 bullets- what you get. final point, you won’t know unless you try- so experiment!! make it possible