This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-22
Channels
- # aws (5)
- # bangalore-clj (3)
- # beginners (84)
- # boot (31)
- # carry (1)
- # cider (6)
- # cljsrn (7)
- # clojure (188)
- # clojure-conj (1)
- # clojure-dev (3)
- # clojure-dusseldorf (8)
- # clojure-greece (10)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-russia (45)
- # clojure-spec (5)
- # clojure-uk (64)
- # clojurescript (83)
- # clr (9)
- # core-async (45)
- # cursive (55)
- # datomic (8)
- # devops (1)
- # emacs (7)
- # graphql (1)
- # hoplon (3)
- # jobs (1)
- # jobs-discuss (37)
- # lein-figwheel (3)
- # leiningen (4)
- # luminus (6)
- # off-topic (5)
- # om (2)
- # onyx (33)
- # pedestal (13)
- # re-frame (9)
- # reagent (28)
- # rum (15)
- # specter (4)
- # unrepl (38)
- # vim (3)
yes, they commented on it all the way through the debates
morning
I'm trying to write a series of blogs on my approaches and personal experiences with software architecture over the last two decades...it's very much a work in progress and I have a long way to go to get to the detail and craft the message but I'd appreciate any retweets or comments/suggestions https://twitter.com/agile_geek/status/864055236435910657
Given the delays I experience on "The Flying Scotsman - The Train" rather than "The Flying Scotsman - The Locomotive" I sometimes think Virgin Trains East Coast keep the train timetable secret! Well random anyway! http://www.bbc.co.uk/news/uk-england-gloucestershire-39991602
@agile_geek I heard that it is used as the random number generator by GCHQ and the NSA 😝
train arrival time delta from timetable seems like a perfectly respectable source of entropy @thomas
https://www.witpress.com/Secure/elibrary/papers/9781845645007/9781845645007009FU1.pdf
it would be awesome to see estimates of the parameters of that distribution for different countries and companies !
in those cases it would also be interesting to include negative lateness - i.e. earliness at signal - to get an idea of how much overcapacity is being used to (almost) guarantee on-time at platform
then we could pit the germans against the swiss in a battle of efficiency
There is a web site here in the NL where you can see what the cause was of the delay. last year 250 times a person was hit by a train.
i like that there are fewer delays on the weekend than in the week in NL @thomas
Maybe fewer ppl get depressed at the weekend?
I've been delayed most often by signal issues, but been delayed a few times due to people hit by train (once by train I was on!) but I wonder if NL suffers from "delays caused by someone nicking 1km of copper signalling cable" which happened to me once!?
I once was delayed earlier this year by person hit by train. not good. and it took a long time to resolve as well.
I saw the driver of my train, he was escorted down the train to the back by two other employees (the guard and the relief driver) about an hour or so after the incident. He was white and shaking.
does anyone know if Clojure has any ability to tell if a form needs to be evaluated each time it is encountered or if it can be evaluated only once?
my assumption is not, in which case, is there some cunning performance macro that can help?
are you looking for memoize
@peterwestmacott ?
…but at the expression level rather than the function level
if I have a function that computes some stuff, and some of that stuff depends on the input, but some of it doesn’t, and all of it gets recalculated every time the function is called
then I can extract the stuff that never changes to a (def ...)
contrived example:
(defn foo [a]
(str (string/join ", " [1 2 3]) " and " a))
the result of string/join will never vary
I could extract it to a def
within the namespace
will a let
prevent re-evaluation on subsequent calls?
oic, put the function definition inside
I heard non-top-level def
/`defn` was bad
right, so why is def-in-def bad?
I would avoid expectations, and test it at the REPL?
so I guess there’s no macro that says ‘compile this to a constant’