This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (5)
- # bangalore-clj (3)
- # beginners (84)
- # boot (31)
- # carry (1)
- # cider (6)
- # cljsrn (7)
- # clojure (188)
- # clojure-conj (1)
- # clojure-dev (3)
- # clojure-dusseldorf (8)
- # clojure-greece (10)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-russia (45)
- # clojure-spec (5)
- # clojure-uk (64)
- # clojurescript (83)
- # clr (9)
- # core-async (45)
- # cursive (55)
- # datomic (8)
- # devops (1)
- # emacs (7)
- # graphql (1)
- # hoplon (3)
- # jobs (1)
- # jobs-discuss (37)
- # lein-figwheel (3)
- # leiningen (4)
- # luminus (6)
- # off-topic (5)
- # om (2)
- # onyx (33)
- # pedestal (13)
- # re-frame (9)
- # reagent (28)
- # rum (15)
- # specter (4)
- # unrepl (38)
- # vim (3)
When a company posts a remote clojure job they are doing to get overwhelmed with applicants, and many of them are going to have significant clojure experience. Even if the company might be perfectly happy bringing in someone newer to clojure, it’s hard to justify not taking the more experienced clojurists applying or the one with that “perfect” skill set.
Does that imply the supply of clojure dev seeking jobs is greater then the demand? That would be ironic, given how much you FUDA you hear about finding devs outside mainstream languages.
If a remote clojure job doesn’t pull a couple dozen resumes pretty quickly, there’s probably something wrong with the position. (pay way out of line or something)
Locally the story is different. If you can only hire locally, it’ll depend on the local community.
We have a really bad situation here in Austin, for example. We have a great Clojure community and several people actively looking for Clojure work. Those f us working here all work remotely, so we haven’t gotten much traction getting local clojure teams going.
New people to the group looking for work don’t have the experience to stand out for the remote positions and don’t have local options. We’ve lost quite a few people who moved to other cities for local jobs. Others have just given up and moved on.
It's an industry problem of siloing developers into language, or holding language knowledge as the premium skill.
When in reality, any developer who learns more than one paradigm is well on their way to being able to work in any codebase with minimal ramping time.
So a good chunk of the solution is to champion team-selected stacks where possible, the current main obstacle being coordination with ops teams to ensure you can deploy a given language to your existing tech stacks.
That's becoming a much simpler process thanks to containerization, but serverless poses the problem anew.
As independent contractors seeking Clojure-only work, that's a much harder sell. As someone working inside an existing company, you have more flex to make those things happen, possibly. But you need a culture that's ready to make that kind of polyglot transition.
it’s not just language knowledge - in order to successfully evolve a long-term project you have to be aware of the ecosystem, design patterns, operational concerns. This knowledge takes way more than a couple of weeks to internalize.
I would argue that the patterns and problems are mostly the same, from an abstract point of view. Thats what code reviews and pair programming are there for. If a team is welcoming and open an experienced developer will be up to speed in a few weeks, no matter the language / ecosystem.
that’s true. However with less popular languages like Clojure the supply of experienced developers usually outweighs demand. You have to either win by having more relevant domain experience, deeper knowledge of the technical bits or lower financial demands.
Yea, thats my experience too. Thats why I look for Engineering / Developer jobs and just dont care about the language. I always remember when I was like 11 a teacher told us a story about actors in the medieval age. They were basically wandering around and had a fixed set of acts that they had memorized. Still they applied for different acts and just took the nights to learn them. Its not different today, one applies with a set of skills which should be much broader than a programming language. Two of the skills have to be the ability to adapt and to learn and to convince the one on the other side 😄
it’s also a completely different world depending on the company - whether you’ll be the first technical employee, the third or the 100th
Yep. That's more on us as developers having marketed ourselves for years as 'code-writers', not 'system-shapers'.
to be fair, it’s usually a long path from a code writer to a system shaper that not everyone reaches, independent of the years of experience
Which is part of the reason I remain interested in some of the propositions of software craftsmanship, despite its supposed reputation.
Love the discussion here y'all. 👍 @fellshard - I'm a big fan of software craftsmanship as a value, but I'm unaware that it has a negative reputation. Can you elaborate? Also, is there like a recognized set of propositions somewhere? If so, I'm unaware of that too.
I think most of the negative reputation stems from Uncle Bob, who's rather polarizing since he takes very adamant, all-or-nothing views on many topics, especially the primacy of TDD.
Funny enough, Uncle Bob and 8th Light have been promulgating Clojure of late as one of their favored tools.
nice discussion. I got a bit frustrated after a couple of months of looking for clojure remote jobs and not even getting to an interview. Not only there are too few remote positions, but most of them won’t even consider people not residing in the US
I understand there are less companies using it, and hiring someone from another country carries a lot of risks, but I found odd than it feels easier for me to get an interview for, say, an Erlang or Elixir position, for which I don’t have any experience
I kind of get the feeling that companies using clojure are less open to remote teams than what I’ve seen in other languages