This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-10
Channels
- # ai (2)
- # beginners (3)
- # boot (113)
- # bristol-clojurians (2)
- # cider (77)
- # clara (43)
- # cljs-dev (48)
- # cljsrn (9)
- # clojure (319)
- # clojure-austin (2)
- # clojure-czech (4)
- # clojure-denmark (4)
- # clojure-france (4)
- # clojure-italy (4)
- # clojure-russia (2)
- # clojure-serbia (10)
- # clojure-spec (79)
- # clojure-uk (64)
- # clojurescript (109)
- # clr (3)
- # conf-proposals (21)
- # core-async (19)
- # cursive (26)
- # datascript (11)
- # datomic (19)
- # devcards (1)
- # emacs (25)
- # figwheel (9)
- # hoplon (31)
- # jobs (7)
- # jobs-discuss (14)
- # leiningen (10)
- # lumo (11)
- # off-topic (37)
- # om (40)
- # onyx (4)
- # perun (8)
- # planck (3)
- # rdf (4)
- # re-frame (40)
- # ring (11)
- # ring-swagger (2)
- # rum (21)
- # spacemacs (2)
- # specter (50)
- # untangled (93)
- # yada (13)
I have been to a few dojo's and really enjoyed. The sole advice I can give is 'just do it' ™
Bore da
@dominicm I tend to navigate rather than drive when group coding in Dojo's with people who have less experience than me. Apart from anything I tend not to use my environment except when demo'ing something simply because of the learning curve for Emacs! 😈
If you get a more experienced group we tend to take turns at the keyboard and you just have to put up with whatever the lowest common denominator editor is or take a few seconds more to push and pull from github.
raises hand: I would be the lowest common denominator 😉
Each group self organises how they want to work but I usually gently encourage beginners to do a fair bit of time at the keyboard
or slowest common denominator
P.S. Morning 🙂
Yeah, me too. My touch typing is a little slow and not greatly accurate!
I spent the first 12 years of my professional career typing with two fingers and a thumb on each hand and looking at the keyboard....
How much time is generally available during the coding section for beginners to ask questions about the code?
however I spent a large part of my first year as a professional programmer writing code on coding sheets with a pen!
As much time as they need
we tend to make sure we have one more experienced dev with each beginner group...
@yogidevbear that depends on the group I think.... but I would encourage people to ask as many questions as they want
they ask questions when they need to
nothing more frustrating then being new somewhere and being ignored. that would be a very unwelcoming experience IMO
To be fair, I'd probably feel most comfortable in the back seat observing the conversation and code and asking questions when I get a bit lost
I tend to volunteer to lead a beginners group just cos some more experienced ppl want to just get stuff done and I quite like coaching/teaching. I hardly touch the keyboard after the first 5 mins
At least for now
@yogidevbear I hear that a lot....and I was like that at my first dojo (when I literally hadn't even read any Clojure... got dragged along by @otfrom)
Wish we had a karma bot on this slack group 🙂
Yeah, I think it would only be the first time that I'd observe like that
The next time I'd try be more involved
However, my experience in that dojo made me ensure that when I'm in a beginners group I gently encourage ppl to take a turn at the keyboard...so @yogidevbear in my group you would end up coding more than you expect!
Haha, ok fair enough
I don't force people but as an example I had two complete n00bs last week, one was a women who was a little shy, and both did about 40 mins each alternately solving 4clojure problems and I typed for about 10 mins in total and answered a lot of questions
I'll make sure to be there when you're at the next dojo
I tend to be at the TW one more than USwitch as I'm knackered on a Monday!
Guess I'll have to try convince my "boss" to give me a London pass to both evenings
@agile_geek Seems interesting, I can either help out beginners or take on some complicated projects with others. Very rewarding.
Yeah. Basically the format is: 1. Eat beer and pizza whiie thinking of ideas for 'projects' 2. Write ideas on white board 3. Everyone introduces themselves, states experience level with Clojure and answers silly question - the last being an @otfrom special! 4. Vote on ideas 5. Organise into teams around 'winning' idea(s) 6. Code for about 1-1.5 hours 7. Every team does show and tell
What sort of time to the meetups usually finish?
@yogidevbear about 10pm assuming start of 7pm but you can leave when you like/need to.
coding usually finishes about 9:15-30 then we have show and tell
Good to know :thumbsup:
@benedek I'm sure I've asked this before but do you know of anything in cljr, CIDER or projectile, etc. that will auto generate a blank test file from the ns in the current buffer. I know this would have to assume naming conventions but CIDER already does that for cider-test fn's
not from the top of my head. also my first idea would be to check yasnippet templates for clojure
@agile_geek if looking at yasnippets, this is the repo for it: https://github.com/mpenet/clojure-snippets
and this is as advanced the blank test file will be: https://github.com/mpenet/clojure-snippets/blob/master/snippets/clojure-mode/test
Not sure yasnippets will help as they generally expand in the buffer your in...I want to create a new file in the test dir for the ns in the buffer. If that makes sense?
i think it does. suppose you want to generate test fn stubs for public defn
s too or something along those lines?
That would be nice ....but initially just creating a blank file in the test tree with a default name and require for clojure.test would be enough
well cljr does part of that: https://github.com/clojure-emacs/clj-refactor.el/wiki#automatic-insertion-of-namespace-declaration
Not sure if this book is of interest to anyone, but...
It's got quite the list of topics covered: https://library.oreilly.com/book/9781787129597/clojure-high-performance-jvm-programming/toc.xhtml
@benedek I know cljr does some of it...use it all the time.
Ah @yogidevbear I was surprised by the title, quite similar to another book I have. It is indeed the 3 books of Packt publishing into one! New thing to me that books get combined like that...
yeah, the async barrier snapshotting looks like it could be really useful