I’ve been interviewing a lot lately. Some good leads, but I don’t like to put all my eggs in one basket. Today, I took a call from a CTO supposedly looking for an Elixir developer... ( #myelixirstatus )
He was indeed looking for an Elixir dev, but then proceeded to explain how he found that Elixir devs were typically subpar compared to Clojure devs, who were typically experts in data flows. Elixir was also apparently fundamentally flawed, and the Actor model was ridiculous.
The previous CTO who he replaced had build their old stack in Elixir, and apparently it was so bad that they had to start from scratch with a “legitimate” tech stack featuring Clojure and its genius devs.
At this point, I’m thinking “Did you just sent out a recruiter to find me so you could tell me I’m beneath your standards?”
But no, he needed someone to actively work on the existing Elixir stack (which he hated) and build features while the real devs built it the right way with Clojure.
I tried to clarify, “So you need someone to maintain your legacy codebase until you make the switch?” But no, the Clojure project was expected to take until 2022 and beyond. They still needed new features in nasty old Elixir until then.
But guess what? The big perk of the job for me: “You can work alongside some great Clojure developers and maybe learn some of their ways.”
At some point he mentioned that all the web should be running on some Lisp dialect because it just made sense. He also mentioned that his company was a great place to work, although he could “be a bit of a hardass <laughing>.”
So long story short, that was a “No” from me. I might also add that I — despite my shortcomings as an Elixir dev using a subpar Elixir stack — built a fintech platform backend in Elixir that continues to handle millions in banking transactions with barely a hitch. #myelixirstatus
• • •
Missing some Tweet in this thread? You can try to
force a refresh
