11–16 of 16 posts
My cut-off criteria at the time were: are they bringing revenue and what technical risk do they open us to (hiring, training, debt, etc.)...
As hinted, the first one I killed was in Python, and I had written about 70% of the codebase.
What is your grief with Clojure (because I'm just trying to get familiar with it)?
Lack of documentation around performance related stuff and high memory usage because of immutable data structure. Otherwise it's great. I try to do it in my free time since most of the clojure services are stable(in terms of features) and we are just scaling it up as we see increase in traffic but it's not really helping right now.
Where I work, we were previously a ColdFusion shop when I joined, and after a false start with Scala, I introduced Clojure and it stuck: we cross-trained the CF devs and slowly rewrote the platform from the bottom up in Clojure.
We had struggled with automated deployments, and the size of servers, when we were a CF shop but after the switch to Clojure we had a fully-automated deployment pipeline, with rolling cluster updates, and much smaller servers than we needed before, running more processes than before.
I killed projects in Clojure when I took over the company. Then again, I killed projects in Scala, and Python, not only including but starting with the ones I had spent more than a year building. About ten projects were killed. My cut-off criteria at the time were: are they bringing revenue and what technical risk do they open us to (hiring, training, debt, etc.)... As hinted, the first one I killed was in Python, an…
Earlier quoted context omitted.
Lack of documentation around performance related stuff and high memory usage because of immutable data structure. Otherwise it's great. I try to do it in my free time since most of the clojure services are stable(in terms of features) and we are just scaling it up as we see increase in traffic but it's not really helping right now.
I guess it depends what the tech stack was before? Where I work, we were previously a ColdFusion shop when I joined, and after a false start with Scala, I introduced Clojure and it stuck: we cross-trained the CF devs and slowly rewrote the platform from the bottom up in Clojure. We had struggled with automated deployments, and the size of servers, when we were a CF shop but after the switch to Clojure we had a fully-…
Now most of the company moved out of Clojure for various reasons but they didn't try to write performant code and instead just chose to rewrite which I want to avoid. Try as much as possible before deciding to rewrite since rewrite is expensive given the codebase has lot of things.
I am glad, it's not Java though.
I killed projects in Clojure when I took over the company. Then again, I killed projects in Scala, and Python, not only including but starting with the ones I had spent more than a year building. About ten projects were killed. My cut-off criteria at the time were: are they bringing revenue and what technical risk do they open us to (hiring, training, debt, etc.)... As hinted, the first one I killed was in Python, an…
What did you replace it with?
My previous company did. In fairness one of the problems the company faced was way too many languages being used in-house. Combined with the difficulty in getting Clojure talent, and it was inevitable that the Clojure went out. The Clojure systems got migrated to Golang and C#
Why bother looking for talent in a specific language? Every reasonably intelligent (not even necessarily talented) developer can learn another high-level language in some weeks.