This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-10
Channels
- # admin-announcements (21)
- # announcements (1)
- # boot (91)
- # cider (2)
- # cljs-dev (46)
- # clojure (77)
- # clojure-berlin (1)
- # clojure-czech (2)
- # clojure-dev (22)
- # clojure-france (2)
- # clojure-india (1)
- # clojure-japan (16)
- # clojure-russia (6)
- # clojure-uk (1)
- # clojurescript (195)
- # cloxp (2)
- # cursive (15)
- # editors (6)
- # jobs (10)
- # ldnclj (18)
- # liberator (3)
- # off-topic (2)
- # onyx (24)
- # re-frame (4)
- # reagent (57)
I'm mainly looking for a set of code samples that I can toy around with using my own ideas
mutability could create implicit dependencies between different components, caused by ordering requirements invisible to code signatures for example. Immutability avoids that
Rich's "value of values" talk
scriptor: here are some slides i put together — minimal “prose” :) https://docs.google.com/presentation/d/1DlqP8Yil13RMbOc4OA4n-juuYQt5-YuN-YKIwH1H9HE/edit?usp=sharing
I'm mainly looking for "here's some code that likely looks familiar to you, here're the problems it can cause"
just take any java code you find on the net then :)
scriptor: Most of the large codebases written and maintained by the teams with some turnover over time can be used, but I'm not aware of explicit "here are the problems" characterisations, those are usually only felt by the team members, not externalized.
Hello!