This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-15
Channels
- # admin-announcements (7)
- # alda (1)
- # aws-lambda (1)
- # beginners (12)
- # boot (20)
- # cider (59)
- # cljs-dev (4)
- # cljsrn (69)
- # clojure (232)
- # clojure-austin (3)
- # clojure-austria (1)
- # clojure-belgium (2)
- # clojure-canada (3)
- # clojure-dev (16)
- # clojure-greece (33)
- # clojure-nl (4)
- # clojure-quebec (12)
- # clojure-russia (12)
- # clojure-spec (27)
- # clojure-uk (38)
- # clojurescript (29)
- # community-development (7)
- # component (53)
- # core-async (16)
- # core-logic (1)
- # datascript (7)
- # datomic (11)
- # editors (7)
- # emacs (69)
- # hoplon (157)
- # keechma (1)
- # lambdaisland (2)
- # lein-figwheel (31)
- # leiningen (8)
- # mount (3)
- # off-topic (11)
- # om (23)
- # onyx (64)
- # planck (2)
- # re-frame (18)
- # reagent (21)
- # specter (118)
- # untangled (145)
- # yada (1)
@tolitius: it would be really educational to the community if you could record some of your coding sessions do you have any such recordings yet by chance?
@onetom: quite a fair request. I don't have codings sessions recorded. Unfortunately the work I get paid for, which would be the most interesting, would not allow me to share much (I suspect it is the case with many people and projects).
I did create https://github.com/tolitius/stater for the purpose of demonstrating the ideas, but these "guys" are quite simple to be very interesting. For example I can just run boot watch speak test
across the whole test sources in a different REPL, and not sweat they run on every code save, since they are very quick.
I did a (remote) talk at Clojure Toronto Meetup, where I dove into code a little bit, and I felt it helped with the discussion, so it may not be a bad idea to record the stater
examples, as I work with them, in case someone finds them useful.