This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-11
Channels
- # aleph (7)
- # bangalore-clj (11)
- # boot (70)
- # cider (11)
- # cljsjs (3)
- # cljsrn (17)
- # clojure (88)
- # clojure-brasil (8)
- # clojure-dev (17)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-poland (8)
- # clojure-russia (2)
- # clojure-spec (44)
- # clojure-uk (32)
- # clojurescript (176)
- # cloverage (2)
- # component (5)
- # cursive (3)
- # datomic (23)
- # defnpodcast (6)
- # dirac (15)
- # emacs (6)
- # garden (19)
- # hoplon (126)
- # leiningen (1)
- # off-topic (3)
- # om (66)
- # onyx (56)
- # re-frame (8)
- # reagent (7)
- # ring-swagger (43)
- # specter (18)
- # untangled (110)
- # vim (3)
- # yada (39)
morning
madainn mhath
The people it bothers aren't in a position to fix it. By the time they are, they've forgotten.
good observation @dominicm
or, the people who can change it have no interest in changing it as it serves them well.
IME when companies a growing then team-level managers see benefits in improving onboarding
@otfrom depends on the company/team. sometimes it takes a long time before you find out all the accounts etc. you need.
otfrom: not my experience
sometimes it is not written down on what to do… and the people who have been there a long time just have all these things.. but no idea how they got them in the first place
glenjamin: interestingly this is a company undergoing rapid growth but I think their processes are lagging behind atm
agile_geek would be great to get your reaction to this: http://blog.cognitect.com/blog/2016/10/5/interactive-development-with-clojurespec
interesting, my initial reaction is that of the 4 properties listed at the start, only > the sum of the values should be <= the number of pegs in the secret code is remotely likely to be accidentally violated
I liked that it started from a pretty basic understanding of the problem and then fleshed it out.
otfrom: I'll take a look tonight
I'd be interested in it from two perspectives: 1. How easily it can be used to understand Clokure.spec given my rudimentary understanding from only reading the pages on spec on http://clojure.org
2. What does a Spec driven workflow look like?
Should have spare time tonight while sitting in Hotel room to take a look and report back
the juxt office working conditions have just got a lot worse, I have nearly 400 unopened bottles of beer behind me in the office and must stay strong...
malcolmsparks: chug, chug, chug...
I guess we should get some bottles of CIDER in for ClojureX for during Bugs talk.
malcolmsparks: BTW lots of ppl talking to me recently saying how much they enjoyed XT16
@agile_geek @malcolmsparks same here at uswitch
@benedek just hoping everyone is as kind about ClojureX this year :)