This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-15
Channels
- # announcements (10)
- # beginners (113)
- # calva (2)
- # cider (75)
- # clj-kondo (1)
- # cljdoc (2)
- # clojure (142)
- # clojure-europe (11)
- # clojure-gamedev (6)
- # clojure-italy (7)
- # clojure-nl (8)
- # clojure-spec (3)
- # clojure-uk (50)
- # clojurescript (47)
- # cursive (7)
- # data-science (22)
- # datomic (12)
- # dirac (3)
- # events (1)
- # fulcro (114)
- # gorilla (1)
- # jackdaw (5)
- # joker (3)
- # kaocha (10)
- # leiningen (1)
- # liberator (2)
- # mount (6)
- # nrepl (1)
- # off-topic (16)
- # pathom (34)
- # pedestal (3)
- # re-frame (19)
- # reagent (11)
- # remote-jobs (5)
- # shadow-cljs (127)
- # spacemacs (12)
- # test-check (15)
- # tools-deps (8)
- # vim (4)
I wrote a thing again, explaining stuff on clojurebridge is good inspiration š
How to analyse whatever problem youāve got to recognise the elements of filter-map-reduce (thereāll be a followup talking about Clojure specifically, and generalised to system design/problem solving): https://www.3jane.co.uk/posts/assembly-line-components/
that's a really nice checklist for how to go about decomplecting a process
I'm not wild about your use of the word 'Dispatcher' though; to me 'dispatcher' means
figure out which method to call
and then call it
and I'd therefore start off a little confusedit is already commonly used, thatās true. I wanted to take the terms from actual production lines; originally that was a ādistributorā. Do you think distributor would work better?
one thing Iād like to convey is that itās possible to have multiple outputs (like: stdout, stderr, log files)
outgoing
perhaps?
er, that would imply an incoming
I guess I'd start looking at something like https://www.thesaurus.com/browse/leave?s=t
and keep going until I found a word I liked
Morning
Anyone interested in MC'ing the ClojureX conference this year?
@jr0cket: @jasonbell would be very interested, but afraid to ask... A good friend told me.
haha like 'Unexpected star of the show'
Iām assuming that @thomas just has a lot of left over fruit that heās saving up.
this could be our double act @jasonbell... think about it.
The person MC'ing would not be a scheduled speaker ideally.
Having a pair of MC's is welcome, it helps with the engagement and helps ensure important things are not forgotten
There would be some training / practice to ensure that the person(s) are comfortable playing that role.
I personally enjoyed the training / practice the @otfrom gave me in 2015, I think it went like this: [9:00] @otfrom does intro [9:10] @otfrom hands microphone to @agile_geek and says "I have to go back to work you can handle this right?" [9:11] @agile_geek makes sh*t up fast to intro first speaker ....
I thought I'd dragooned you before I did the intro. I'm sure it felt the other way around tho. š
We will be expecting a little bit more this year š
nice montecarlo article @jasonbell https://dataissexy.wordpress.com/2019/04/15/finding-pi-with-montecarlo-method-and-clojure-math-justmath/
one question I do have for you data-science types is about
clojure.test.check.generators/generator-fn
it takes two seed values, a mean and a variance in order to be able to point the test generator at interesting parts of the dataset
I donāt see that function anywhere š
butI've not seen that aspect of generators get used heavily; is that because it is flawed?
or there are better ways to trawl the search space
or I'm not looking properly and its' being using extensively all the time
I think it was intended to be able to automatically zone in on troublesome parts of the input domain
But I don't think I've ever actually seen it do that