📎 Webclip
All in
The author announces a public commitment to go “all in” on Elixir after already spending several months mostly focused on it. This means seeking only Elixir work, contributing to Elixir open source, speaking primarily at Elixir or broader functional programming conferences, and likely writing about Elixir topics. He explains that Elixir suits how he thinks and develops, lets him work quickly, and offers fast tests, simple functional patterns, clear error messages, and a supportive community. He also describes how market conditions, a maturing ecosystem, and personal time constraints with family pushed him to choose Elixir over splitting attention with Ruby, while still valuing Ruby and its community.
Reading notes#
- The post exists because the author had to repeat the same explanation in long emails and wanted a reusable reference.
- He states he is going all in on Elixir, having already been heavily focused on it for a few months, and now wants to make that choice public.
- His commitment covers only seeking Elixir jobs, doing Elixir open source work, speaking at Elixir or functional programming conferences, and probably only writing about Elixir.
- He says Elixir “just really resonates” with him after nearly three years of use, with about two years of serious usage.
- He describes Elixir as the perfect language for him because it matches how he likes to develop and think, and he feels fast and productive when writing it.
- Fast test execution is highlighted as a key benefit, with entire test suites running in seconds instead of minutes, which he ties directly to higher development productivity.
- He values the simplicity of Elixir and functional programming, contrasting it with needing to memorize many design patterns and code smells in other environments.
- He notes that in Elixir he mostly works with functions and data, with decisions focused more on naming than architecture.
- This simplicity lets him spend more time on the problem domain instead of dealing with the complexity of code structures.
- He contrasts Elixir with Ruby, pointing out that Ruby can be a very sharp tool where people often “cut themselves” with advanced features like
instance_exec. - In his experience over two years of serious Elixir use, the language’s simpler paradigm has not limited his ability to solve needed problems.
- Referential transparency in Elixir reduces the amount of information a developer must hold in their head at once.
- He acknowledges that large-scale distributed systems are always somewhat tricky but says they are simpler when built with Elixir.
- The author praises the Elixir community’s growth, describing it as strong, with leaders who mentor others and have personally helped him many times.
- He emphasizes that core team members are approachable and kind when offering help.
- Error messages in Elixir are described as very good, with the core team actively working to improve them, which he considers significant.
- One reason for the timing is that, without deliberate effort, most incoming work for him over the past six months has already been Elixir-based.
- He contrasts this with two years earlier, when most requests were for Ruby projects, noting the shift in demand without explaining its cause.
- Because of this shift, he feels confident that focusing on Elixir will not endanger his livelihood.
- Another factor is that the job market for Elixir developers has grown, so client companies would no longer struggle as much to train or hire for Elixir projects.
- He believes the Elixir package ecosystem has matured to the point where there is usually a high-quality library solution for most needs.
- He notes that developers often no longer need to write tools from scratch, and while Elixir lacks JavaScript’s surplus of options, having one strong solution for each problem is enough for him.
- Personal life constraints also drove the decision; he describes being very busy with two young children and a wife who works as a successful opera singer.
- He mentions being halfway through 12 weeks of travel for his wife’s performance gigs, which amplifies the pressure on his time.
- He found he could not do everything he wanted in both the Ruby and Elixir worlds while also maintaining work and family time, which forced a choice.
- Although the decision was difficult, he believes focusing on Elixir is the right choice for his situation.
- He clarifies that he is not absolutely abandoning Ruby, saying that writing Elixir makes him happy, but financial goals like paying off family student loans also matter.
- He frames language choice as one part of job satisfaction, not the only factor, and calls Ruby a great language that inspires strong loyalty in others.
- For the right opportunity, he would consider working in any language, showing some flexibility despite his stated Elixir focus.
- He suggests that in a different life with more available time, he might not have needed to choose between language communities.
- He does not expect to completely separate from the Ruby community, which he praises as full of great people.
- He credits the Ruby community with making him love the language originally and says that connection prevents him from fully leaving.
- He anticipates that his involvement with Ruby will lessen, particularly in terms of conference attendance, possibly for a long time.
