This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # alda (8)
- # aws (1)
- # bangalore-clj (1)
- # beginners (55)
- # boot (114)
- # capetown (2)
- # cljs-dev (51)
- # cljsjs (1)
- # cljsrn (14)
- # clojure (119)
- # clojure-belgium (6)
- # clojure-brasil (9)
- # clojure-conj (2)
- # clojure-greece (1)
- # clojure-korea (2)
- # clojure-poland (12)
- # clojure-russia (64)
- # clojure-spec (12)
- # clojure-uk (60)
- # clojurescript (159)
- # code-reviews (2)
- # component (4)
- # core-matrix (2)
- # cursive (79)
- # datascript (7)
- # datomic (2)
- # defnpodcast (4)
- # events (2)
- # hoplon (13)
- # jobs (2)
- # lein-figwheel (1)
- # off-topic (10)
- # om (42)
- # onyx (60)
- # pedestal (5)
- # perun (7)
- # rdf (4)
- # re-frame (4)
- # reagent (21)
- # ring-swagger (25)
- # schema (1)
- # spacemacs (52)
- # specter (1)
- # utah-clojurians (1)
- # yada (5)
Hello @agile_geek for the ClojureX panel, how about the topic of "Guiding people into Clojure". There is a lot of scope for discussion on this topic
Sharing ideas on how to encourage and support others also helps our community grow our community
I've mentored a few people into Clojure this last year and it's been very interesting feedback. For example, I was a little surprised that not everyone likes http://braveclojure.com, atom editor is much preferred over LightTable and Nightcode by many, a lot of people want to learn Emacs because of Clojure. The most positive thing I've heard quite often is that Clojure is surprisingly easy to learn.
@jasonbell How are this crisp morning? Good idea. I'm beginning to feel this is more a park bench than a panel and we circulate speakers and audience members in and out of the 'panel'. that way we can address a number of different topics and see what other topics this leads too. I just need some of the speakers to sign up to get the ball rolling so would be great if you can step up.
@agile_geek I’m well thank you, NI is a wee bit snowy but the rain soon put a stop to that.
Looks like you may be in for some wind over the weekend too? I'm glad I'm back up north at weekend as I think we'll miss most of it.
No weather warnings so I’m not overly panicking. Worst snow usually lands in March.
@jr0cket Indeed Clojure is surprisingly easy to learn. I was able to do first Onyx contribution after 3 months learning Clojure and doing small example project.
@jr0cket @mariusz_jachimowicz I am always slightly taken aback that people say Clojure is easy to learn....it just shows how: a) slow I am at learning, b) set in my ways I am, as I found it quite challenging.
I had to unlearn loads of stuff I was carrying around as baggage from 16 years of Java at the time plus 28 years of imperative programming!
It took me a year to unlearn things so I could open my mind to functional ways. I see Clojure as a life lesson now.
I have heard that Clojure is (or functional programming in general) is easier/simpler to pick up for programming novices. and more complicated for people who have done OO/imperative/mutable programming
Yeah, the problem is generally that we often are married with language or paradigm.
@thomas I recently archived off every Java project I had, every Java startup idea that was gathering dust then deleted Eclipse. So it left me with just Clojure and Emacs and nothing else.
Did the same with bass guitars and the Chapman Stick, sold all the basses so I could only focus on the Stick. It worked.
It's hard for me when I see long functions with a lot of transformations. I love code that is very idiomatic based on
Don't force me to think idea 😄
I keep meaning to get my wife into clojure - her background is pure mathematics, so it should be pretty natural for her
I keep meaning to get my wife into clojure - her background is wedding dress making, so it should be… oh wait.
although at one point I had a static site generator set up for her business website, and the config files she was editing were clojure source files
My wife does our accounts hacking EDN in Emacs and pushes through git into a datomic backed accountancy system that @malcolmsparks wrote. Amazing we're still together.
🙂 Sometimes it’s better to have a diverse partner than one with too much shared context. Our entire lives are dominated by kanban walls and other agile planning artifacts
I have previously wondered about applying agile techniques (eg. weekly retrospections) to relationship management - but I think its more of a ‘comedy sketch’ type idea than something that real humans would want to do.
@agile_geek: I do not think you appreciate how much Clojure you actually do know...
We did daily standups in the run-up to our wedding, to walk through the wedding trello.
@korny In my very small experience mathematicians have a very different idea about the meaning of ratio, but otherwise understand Clojure quite well
an agile trainer i did a course with ages ago said he used a kanban board and retros at home
Personal Kanban has many interesting stories... There is one of a working mum using Kanban to have a much better open and honest relationship with her daughter. Wedding planning, moving house and many other very stressful activities can be made better by using Kanban effectively...
For those mentioning about getting their partners into Clojure, just a reminder we have ClojureBridge on 26th November.
We’ve encouraged my sister-in-law to set up a kanban wall for her family tasks - it’s been very useful so far. You don’t really need any IT knowledge to use it like a shared multi-stage to-do list - and it’s handy to point people to Trello if they want to move it online.
reminds me of the focus of what kanban is actually about as well - limiting WIP and visualising progress
> … is easier/simpler to pick up for programming novices. and more complicated for people who have done OO/imperative/mutable programming @thomas: I think one of the biggest problems I’ve seen with people coming from OO debugging clojure, is that they don’t yet trust its promises… i.e. immutability really is a promise, and you very rarely have to worry about things changing underneath you… I’ve noticed beginners debugging still tend to look for bugs in the kinds of places they’d find them if they were programming with mutable state… rather than stopping and thinking - the language guarantees this won’t happen, what other explanations are there?
obviously the promise is only mostly true, because it’s not entirely pure - but it still changes the order in which you should proceed with your bug hunt
I found the weirdest bit was trusting that I didn’t need to encapsulate all my state
Getting used to laziness by default was also a headache - especially when trying to diagnose / debug! I’ve thought in the past that for some situations, it’d be quite nice to be able to disable all laziness. Except of course that’d break a whole lot of language internals.
November 24th talk for London Clojurians announced - https://www.meetup.com/London-Clojurians/events/235676436/