Hi,

I based a recent presentation in a local user group on the bank account 
example: two accounts, deposit, withdrawal, transfer. Starting with maps. 
Building the code. Noticing that no locks are required. Replacing maps with 
records w/o changes to underlying code. Easily testing pure functions. &c. 
&c. There was a lot of positive feedback. (Although I don't know how far 
things will get.) It was a two hours live session with many questions from 
the auditorium and ad hoc examples.

The advantage of the bank account kata is that chances are that people know 
this already in other (maybe OO) languages. So they can easily compare with 
their experiences. (In fact the same kata was discussed for OO languages in 
December in our user group.)

Meikel

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to