Fork me on GitHub
#jobs-discuss
<
2020-02-21
>
seancorfield17:02:20

@markgdawson One possibility is to introduce Clojure where you already work (that's how we shifted to Clojure at work). Not all companies will allow that but if you work somewhere that is already polyglot, and already on the JVM, then it might be relatively straightforward to use Clojure on a small but visible project and show folks how well it does.

💯 1
andrea.crotti18:02:07

that might also backfire, specially if you're the only person who likes/is interested in Clojure

1
andrea.crotti18:02:39

it is in theory much better to find a place which is already sold on Clojure, but depending on where you live they are not so many

M4rkD18:02:22

Thanks @seancorfield, that's an option for sure. Unfortunately, I think that a big ask, as we work on code from outside our control, and the code is a deliverable. Small hobby/internal projects, sure. Something serious, very unlikely unfortunately. But otherwise, I think for many it's sound advice.

M4rkD18:02:18

@andrea.crotti I've already started carefully downplaying my enthusiasm for Clojure for fear of broken record syndrome! I've not been met with too much shared enthusiasm yet. :)

M4rkD18:02:54

Geographically, I think I'm restricted to remote work realistically. Not a huge amount of tech around here, and certainly no Clojure I'm aware of.

the2bears22:02:55

@markgdawson here is my story, starting from the point where I have years of Java but am burnt out and frustrated with its concurrency model: • Started programming Clojure in my spare time, chose an existing Java arcade game I wrote to do in Clojure as a personal learning exercise. Fell in love. • Gave a lunch & learn at work, showcasing the Clojure game and showing REPL development. • Used Clojure for internal "quick" stuff. Kept a REPL running. When asked if the "distribution of our IDs is uniform" worked up a quick test, with visual graph, on the spot. • Started interviewing for Clojure roles. Wasn't good enough, but learned more. • Finally landed a Clojure role, took it and left Java behind. • Turned that into my present role and while I don't work exclusively with Clojure, I'm a happier person than before.

M4rkD14:02:17

Hi @U0QNQ3P3L, thank for sharing the story. I feel like I'm probably still in the "wasn't quite good enough" stage of the journey, but I've picked up a few side projects to sharpen my skills. A lot of it is probably a waiting/learning game for me right now. 🙂

M4rkD14:02:46

How did you find it when you started applying for jobs before you were "good enough". Did you find employers wanted evidence of bigger projects, or was it more a question of being able to demonstrate competence (e.g. technical questions and competence testing)?

the2bears17:02:55

@markgdawson, it was all the latter. Most of the Clojure positions I applied for had small assignments to complete up front. All had Clojure coding during the interviews.