This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-20
Channels
- # beginners (7)
- # boot (39)
- # braid-chat (3)
- # braveandtrue (1)
- # cider (27)
- # cljsjs (15)
- # cljsrn (6)
- # clojars (18)
- # clojure (307)
- # clojure-art (1)
- # clojure-brasil (1)
- # clojure-italy (2)
- # clojure-poland (3)
- # clojure-russia (61)
- # clojure-sdn (2)
- # clojure-taiwan (4)
- # clojure-uk (5)
- # clojurebridge (7)
- # clojurescript (19)
- # core-async (1)
- # core-matrix (1)
- # cursive (35)
- # datomic (3)
- # emacs (51)
- # euroclojure (3)
- # hoplon (20)
- # jobs (1)
- # keechma (1)
- # mount (3)
- # off-topic (2)
- # om (177)
- # onyx (96)
- # parinfer (4)
- # pedestal (4)
- # re-frame (19)
- # reagent (7)
- # untangled (5)
@mchampine: In what ways was it successful?
Everyone got a Clojure dev environment installed: Success #1! The curriculum seemed to work too. We created and used a new curriculum fork with Nightcode as the IDE. Good student/mentor ratio (under 3 :1). Those new to programming made impressive progress working through the tutorials with their mentor's help, and mini instruction sessions explained concepts like "map" which were readily absorbed and used. Great "women in technology" panel session. Warm social atmosphere with lots of positive interactions throughout. We left with a good feeling, including the mentors. There's only so much you can do in 1 day. We said our goal was to give everyone a "taste" of programming in Clojure. They got that, and the taste was mostly appealing. Btw, in many ways the "new to programming" group had it easier. They didn't have that first jarring step of "unlearning" the imperative approach to problem solving.
My experience has been exactly the same with the new to programming vs programmers in the 3 workshops that I have been a TA at, mchampine