3 ms·

Honestly, maybe don’t. You love Clojure, that’s awesome. But introducing it at your company if it does not have a lisp culture already might not go so well. You

by lelag 2y ago

Honestly, maybe don’t. You love Clojure, that’s awesome. But introducing it at your company if it does not have a lisp culture already might not go so well. You say so yourself: lisp dialects like Clojure come with a steep learning curve, and not everyone will appreciate the shift, especially if they're comfortable with the current stack. Forcing it on your team could create frustration, confusion, and a lot of resentment, not just toward the language, but possibly toward you. Sure, you might convert a person or two, but most will likely see it as unnecessary complexity. If you really want to write Clojure every day, you might be better off finding a company that already embraces it instead of trying to turn your current team into Clojurists. Sometimes it’s better to enjoy something for yourself than to make it everyone else’s problem.

_xiaz 2y ago
I'll second this. Many people are happily complacent with mainstream languages. A minority ventures out in $lang of the day for the fun of it, with functional languages being an even smaller minority. At a minimum, build some strong clojure skills first, such that when you introduce it to anyone else, you can do so with confidence
defyonce 2y ago
it is better to have +1 company with Clojure (potentially hiring), than +1 Clojure dev looking for work
- MarkMarine 2y ago
  It’s not too hard to point to NuBank’s success and say we can be like that, my C-suite is already on board. Hopefully we’ll be +1 hiring for Clojure in the next year if I’m successful
MarkMarine 2y ago
I spent a lot of time in my early career jumping from company to company looking for the next better thing, be it tech stack, job title, pay package. It worked quite well for me early on, until I interviewed for a principal engineer role at Branch and the VP said something that struck right to my core… that I had a good interview and good experience but my work history showed someone who wouldn’t be there in two years, and they were hiring for a long term role. I’ve vowed since then to stick it out, to work hard building something better at the companies I work at, and to make it obvious from my resume and day to day that I care about being somewhere long term. I take the idea of leaving my campsite better than I found it seriously, and if Clojure was just a fun hobby for me I wouldn’t try to introduce it at work. I think my colleagues can learn a lot from the language and paradigms that are at the core of the language, my hope isn’t that we re-write our stack in Clojure, or even that the services I write in it persist past when I leave. My hope is that I can use it as an example to show the other engineers I work with a better way, even if we do it with go in most of the stack.

by lelag 2y ago

_xiaz 2y ago

I'll second this. Many people are happily complacent with mainstream languages. A minority ventures out in $lang of the day for the fun of it, with functional languages being an even smaller minority. At a minimum, build some strong clojure skills first, such that when you introduce it to anyone else, you can do so with confidence

defyonce 2y ago

it is better to have +1 company with Clojure (potentially hiring), than +1 Clojure dev looking for work

MarkMarine 2y ago
It’s not too hard to point to NuBank’s success and say we can be like that, my C-suite is already on board. Hopefully we’ll be +1 hiring for Clojure in the next year if I’m successful

MarkMarine 2y ago

I spent a lot of time in my early career jumping from company to company looking for the next better thing, be it tech stack, job title, pay package. It worked quite well for me early on, until I interviewed for a principal engineer role at Branch and the VP said something that struck right to my core… that I had a good interview and good experience but my work history showed someone who wouldn’t be there in two years, and they were hiring for a long term role. I’ve vowed since then to stick it out, to work hard building something better at the companies I work at, and to make it obvious from my resume and day to day that I care about being somewhere long term. I take the idea of leaving my campsite better than I found it seriously, and if Clojure was just a fun hobby for me I wouldn’t try to introduce it at work. I think my colleagues can learn a lot from the language and paradigms that are at the core of the language, my hope isn’t that we re-write our stack in Clojure, or even that the services I write in it persist past when I leave. My hope is that I can use it as an example to show the other engineers I work with a better way, even if we do it with go in most of the stack.