This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-05
Channels
- # adventofcode (41)
- # bangalore-clj (4)
- # beginners (283)
- # boot (62)
- # clara (9)
- # cljsrn (3)
- # clojure (112)
- # clojure-brasil (1)
- # clojure-greece (1)
- # clojure-korea (6)
- # clojure-russia (99)
- # clojure-spec (29)
- # clojure-uk (12)
- # clojurescript (34)
- # clojurex (5)
- # core-logic (1)
- # cursive (31)
- # datomic (30)
- # devcards (5)
- # editors (19)
- # emacs (31)
- # events (5)
- # garden (4)
- # hoplon (137)
- # lein-figwheel (3)
- # luminus (4)
- # mount (7)
- # off-topic (7)
- # om (18)
- # om-next (3)
- # onyx (88)
- # proton (1)
- # protorepl (6)
- # re-frame (48)
- # reagent (15)
- # spacemacs (41)
- # testing (1)
- # untangled (2)
- # yada (18)
@svenhuster we do some scheduling logic, but not the actual creation of events. My advice would be to spike on it and see where you get. Pick a nontrivial subset of your logic, and see whether it gives you what you’re looking for
@mikerod Thanks again for the talk, and for the chat afterwards. It was awfully cathartic to talk to folks with similar problems in healthcare, and the rules engine space in particular.
svenhuster I agree with devn that one of the best things you can do is try to reason about your problem through some examples actually trying to use Clara rules and a rule-driven approach
I often thing that http://www.jessrules.com/guidelines.shtml
Jess (an older rules engine written in Java, with a Lisp-like DSL) has some reasonable guidelines