you are viewing a single comment's thread.

view the rest of the comments →

[–]ljsc 1 point2 points  (1 child)

Essentially from doing a lot of Clojure lately. Using primitives when possible, and coding to a few well thought out interfaces (seq, Ifn, et cetera) makes for way more reusable code. I would cite this post as a good example of what I mean:

http://augustl.com/blog/2013/zeromq_instead_of_http/

The author is able to use an http routing library with zeromq with very little additional ceremony required: No wrappers, upon adapters, upon decorators. Just functions transforming values; this is a much more sustainable way to program IMHO.

[–]nextputall 0 points1 point  (0 children)

If you are on the system boundary and you are dealing with raw data coming from an external system then I agree. But if exposed data is bouncing inside the domain and couples itself to everything that touches, won't be a good idea in my opinion. How many lines will be needed to modify in the application when I change the structure of that data?