Completely agree. I feel no pressure to constantly upgrade my Elixir versions. I just look at the changes and there is often useful features that make me want to upgrade, as opposed the feeling of dread when I am pushed to upgrade.
Really interesting post. I ran into some of the limitations of working with tables and LLM's last year.
I experimented with an approach to use the llm to generate a bespoke transformation machine that uses an LLM to generate a series of transform steps to extracting key data from large data sets.
One aspect of using LLM's to code that I have not seen mentioned is the "loss of attachment" to code in my projects.
For example, working on my project (https://mudg.fly.dev) I wanted to experiment with a new FE graph library. I asked an llm the fantastic (https://tidewave.ai) and it completely implemented a solution, which turned out to be worse than the current solution.
If I had spent many hours working on a solution I might have been more "attached" to the solution and kept with it.
Have you considered that LLMs are also biased against new languages and libraries, so the code quality will be worse compared to something more established regardless of what you personally think/feel?
The ability to have access to the context of the code, run tests and edit the code in place, are capabilities I could not even dream about when I started coding.
How Jose manages to see the potential of a technology (Erlang, LLM's) and produce something so elegant and useful is amazing. It has certainly changed my life.
reply