This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-10
Channels
- # aleph (2)
- # arachne (1)
- # beginners (5)
- # boot (33)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (26)
- # clojure (33)
- # clojure-austin (7)
- # clojure-belgium (6)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-fr (1)
- # clojure-hamburg (1)
- # clojure-nl (11)
- # clojure-portugal (3)
- # clojure-russia (14)
- # clojure-spec (35)
- # clojure-uk (28)
- # clojurescript (49)
- # component (7)
- # core-async (75)
- # cursive (13)
- # datomic (15)
- # dirac (57)
- # emacs (5)
- # events (1)
- # hoplon (34)
- # jobs (2)
- # jobs-discuss (8)
- # lambdaisland (1)
- # lein-figwheel (7)
- # leiningen (3)
- # om (5)
- # onyx (8)
- # re-frame (56)
- # reagent (13)
- # testing (7)
- # untangled (30)
- # vim (51)
- # yada (17)
Morning
@agile_geek I assume this means that you have something lined up?
@thomas It does. Start a new contract today. I'll talk about it once everything signed up and I'm settled in.
@mccraigmccraig would clj(s).spec have caught it?
@thomas i don't think it would - the error was internal to a function - the input was valid and the output was valid, but there was a bad assumption about the form of the input inside the function
@mccraigmccraig How do you mean "about the form"?
@dominicm "about the shape" would maybe have been a better phrase
@mccraigmccraig That seems to me that "input was valid" is not a true statement then. What the function expected, and what was valid (to who?) was different.
@dominicm the input was valid, but the body of the function failed to deal with the full variety of possible inputs
how did you discover the error @mccraigmccraig ? just thinking out loud here is that .spec could have generated that particular input.
@thomas i discovered it because it caused a model inconsistency - better tests in the area would certainly have discovered it, but the set of required tests for complete coverage is a lot harder to construct than it would have been for a type-checker to notice the missing branch
We're hiring for clojure and devops at Mastodon C http://www.mastodonc.com/hiring/2016/10/02/senior-devops.html
your architecture buzzwords look very like mine @otfrom
mccraigmccraig they always have. I'm not sure if that is b/c we have a hive mind or if I'm a fanboi
@minimal in constant memory plz