This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-19
Channels
- # announcements (13)
- # asami (43)
- # babashka (35)
- # beginners (175)
- # calva (23)
- # cider (5)
- # clj-kondo (68)
- # cljsrn (4)
- # clojure (61)
- # clojure-australia (7)
- # clojure-europe (20)
- # clojure-gamedev (59)
- # clojure-israel (11)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-norway (21)
- # clojure-spec (12)
- # clojure-uk (43)
- # clojurescript (9)
- # cursive (56)
- # data-oriented-programming (5)
- # datascript (1)
- # events (1)
- # fulcro (16)
- # honeysql (46)
- # leiningen (1)
- # malli (4)
- # off-topic (12)
- # pathom (46)
- # re-frame (24)
- # reagent (14)
- # reitit (1)
- # reveal (8)
- # rewrite-clj (16)
- # ring (13)
- # sci (9)
- # spacemacs (14)
- # specter (2)
- # sql (2)
- # tools-deps (1)
- # vim (2)
Morning. For me today, judging by my last clojure-learning session: in which I comprehend for the 1000th time (at least) that I should pause to read more docs when learning new stuff. The urge to dive in and try to make something can be overwhelming.
I feel your pain.
Morning all
I'm often reminded of a quote early in The Diamond Age where, from memory, an engineer is manually trying to fit things together in violation of the generally appreciated rule of doing the math / thinking it out.
I like to bounce: skim docs to get concepts, go build things, then bounce back to the docs when you think "oh maybe that thing would be useful"
@lsenjov I do that too. Still often feel a tension between reading in the sort of depth that (I know from experience) saves later frustration, and just writing code. Oddly, this has little to do with work-time pressure - same happens when (like now) I'm doing stuff for learning/pleasure. Quality of docs makes some difference here - if a language feature or library is poorly documented, then reading can be particularly unrewarding.