This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-23
Channels
- # aleph (14)
- # announcements (2)
- # babashka (8)
- # bangalore-clj (2)
- # beginners (66)
- # calva (8)
- # cider (1)
- # clj-kondo (24)
- # cljdoc (3)
- # cljs-dev (3)
- # cljsrn (2)
- # clojure (197)
- # clojure-europe (1)
- # clojure-india (5)
- # clojure-italy (4)
- # clojure-nl (27)
- # clojure-uk (18)
- # clojurescript (56)
- # code-reviews (19)
- # core-async (86)
- # cursive (16)
- # data-science (1)
- # datomic (16)
- # docker (3)
- # events (1)
- # fulcro (101)
- # graalvm (7)
- # graphql (16)
- # jobs (1)
- # jobs-discuss (6)
- # kaocha (4)
- # luminus (1)
- # off-topic (93)
- # onyx (3)
- # pathom (9)
- # planck (2)
- # re-frame (8)
- # reagent (3)
- # reitit (3)
- # remote-jobs (3)
- # shadow-cljs (21)
- # test-check (3)
- # tools-deps (21)
- # vim (16)
Hello, we are looking for another 10 volunteers (~20 total) to coach students at ClojureBridge London on 21/22 of February.
Most of our students are just starting to code, so if you know def map reduce filter
then you know enough to coach. Take a look at the learning paths, all aimed at beginners.
https://clojurebridgelondon.github.io/#learning-paths
Coach training is on the 4th February and I am available to answer any questions about coaching.
Sign up for coaches and students:
https://www.bridgetroll.org/events/500
Thank you.
FYI, the confirmation email when you sign up went to my spam folder in gmail. Not sure if there’s anything you can do about it
The only thing I can think of is to ask everyone to add the sender email address to their Gmail contacts. Open to any other suggestions. Thanks for raising this issue and for signing up.
As you coached at the last event we ran, you do not need to attend the coach training session this time. Thank you for volunteering. If I add anything to the information I gave out last time, I will let you know, but nothing much is planned except maybe an update to how we recommend installing Clojure on Windows.
of course i decided to deploy my unrollbackable change to prod just minutes before the problems started ...
... and of course the deploy went wrong ... so now I can't access the logs to see what's wrong with my app 😞
@UAEFFG05B Would running the app locally with Heroku local help? https://devcenter.heroku.com/articles/heroku-local