This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-05
Channels
- # beginners (3)
- # boot (205)
- # cider (41)
- # clojars (1)
- # clojure (76)
- # clojure-colombia (1)
- # clojure-dusseldorf (3)
- # clojure-russia (314)
- # clojure-sg (1)
- # clojurebridge (1)
- # clojurescript (115)
- # css (2)
- # cursive (5)
- # editors (2)
- # funcool (2)
- # hoplon (18)
- # jobs (62)
- # jobs-discuss (28)
- # ldnclj (1)
- # leiningen (10)
- # mount (9)
- # off-topic (4)
- # om (93)
- # parinfer (10)
- # proton (1)
- # re-frame (19)
- # ring-swagger (18)
(I say that, because I am going through the list of companies that use clojure listed on the clojure website, trying to get another remote clojure job)
I have to agree with hiredman. I've been privy to a number of senior Clojure devs' job searches over the past few months, and every single one of them was looking for remote positions only. If you are looking to hire senior Clojure people and having trouble, I'd say it would be worth the trouble to invest in building a remote team. My $.02.
I'd be curious to know how senior remote devs mentor juniors
or hear stories about having successfully graduated a junior to a senior on a remote team... i've never seen it done in my own experience, but my experience is narrow
Lots of pairing initially, giving them lead on small, well-specified projects on which they can make mistakes and iterate on ‘em
i have a 6 person team, of which we need one more senior clojure backend programmer... and nobody appears to be willing to relocate and/or in the area
that works out pretty well, but it's always a gamble -- it must require the remote engineer to be very communicative
so anyway, i've shifted my focus on getting people that have some affinity with FP in general trained in clojure
and we can do that by using "teamboosting" with seniors who help out a few hours a week
well, if you miss it too much, and would enjoy working at a startup... give me a call
but one of the things was, I was only one of two people at the company who did it. I wasn't really part of a team
@alandipert: so I just spent five years working for a company where the devs were all remote, and as others have mentioned initial hires spent a while pairing, and then we had a very strong code review practice
@lmergen: you could post a message to the clojure meetup mailing list for a job of course
generally, when I interview, the reasoning I get for requiring people to be onsite is something like "we are trying to build a close knit team", which is crazy to me, I am still in touch with most of the team members from that job that was 100% remote. we have almost an alumni thing going on
@hiredman: it is more difficult when it's mixed remote and on site probably. The people who are remote miss a lot that way. When everybody is remote, it's easier, because all communication happens online
oh sorry @dottedmag i didn't see your msg
On the topic of remote teams, I watched this talk by Floyd Marinescu. Found it quite interesting. https://www.youtube.com/watch?v=i71bbQqdy0M&list=PLJNI511LYmA48dKjzQUSIgVz13Zg9NXZC&index=5
Worth viewing the entire talk