Clojure values

About a week ago I put up a poll asked questions about what people in the Clojure community valued. In particular, this was a series of questions that said, “We value X over Y”. I was trying to capture the same notion from the agile manifesto where they say that while there is value in the thing on the right, we value the thing on the left more.

By the way fellow Clojure enthusiast: Clojure/West is coming up March 16-17th in San Jose, CA including keynotes by Rich Hickey and Stuart Halloway! Regular registration rates end Feb 17th.

Here’s the raw data:

Value	Emphatic yes	Yes	No	Just the opposite	Votes	Score	Scaled score
Simple over easy	46	30	3		79	119	1.51
Values over variables	47	27	5		79	116	1.47
Clarity over terseness	24	32	6		62	74	1.19
Practical over promising	15	41	6		62	65	1.05
Thinking over tests	22	44	11	2	79	73	0.92
Public over private	17	49	13		79	70	0.89
Explicit over implicit	14	36	12		62	52	0.84
Data over interfaces	20	43	14	2	79	65	0.82
Accessibility over encapsulation	23	38	17	1	79	65	0.82
Eggs over easy	21	14	24	20	79	-8	-0.10
Code over ideas	5	29	24	21	79	-27	-0.34

The first 4 columns above are the actual votes. Votes was the number of votes cast (I added a couple after the start). Score is my own concoction: +2 points for emphatic yes, +1 point yes, -1 point for no, and -2 points for opposite. That yields a score, which I scaled by the number of votes in the last column. I then sorted by the last column. All data here.

So, glean from this what you will. Some other suggestions that did not make it into the poll:

Pure functions over procedures
Declarative over steps [me: imperative?]
Semantic clarity over syntactic clarity
Simplicity over complexity
Open over closed
Malleability over rigidity
Transparency over secrecy
Contribution over consumption

Pure Danger Tech

Clojure values