<story><title>Bringing Clojure programming to Enterprise (2021)</title><url>https://blogit.michelin.io/clojure-programming/</url></story><parent_chain></parent_chain><comment><author>dgb23</author><text>&amp;gt; A first element of decision lied in the fact that our product used a great number of data structures and business management rules which aim to evolve very frequently and be adapted to new business contexts over time.&lt;p&gt;They seem to have a very good use case for Clojure adoption. The article mentions many of the affordances Clojure gives you for data oriented, information processing problems.&lt;p&gt;But one of the unsung heroes of Clojure is the namespaced keyword:&lt;p&gt;If you’re already working in a FP, data oriented style but in a language that doesn’t have them, I recommend you have a go with Clojure and explore them.&lt;p&gt;It’s such a simple construct that gives you a lot of leverage in terms of semantics, code organization, flexibility and validation.&lt;p&gt;Think of them as having characteristics of uuids, URLs, URNs etc. they stand on their own and have meaning across system boundaries.&lt;p&gt;It’s very nice and calming to have that in-built as an everyday construct.</text></comment>
<story><title>Bringing Clojure programming to Enterprise (2021)</title><url>https://blogit.michelin.io/clojure-programming/</url></story><parent_chain></parent_chain><comment><author>speed_spread</author><text>Makes total sense once you learn that parentheses are all little tyre cutouts bouncing around.</text></comment>