Get AI code generation tools to create correct Elixir code, or else 😱

Sorry if I’m overthinking this.

To date, Elixir is my favorite language. I don’t think of reaching for another language if I don’t have to… until recently.

Have ya’ll seen how good ChatGPT and Github Copilot are? People are just writing their boilerplate code, and even nuanced code lightning fast :astonished: Only catch is, it’s usually Python or Javascript. I don’t want to use those languages today, but I do want to ship apps ASAP. Seeing how fast these AI tools are generating mostly correct code that is easily tweaked has me reconsidering using Python and Javascript :person_shrugging:

Also, once businesses catch on to the productivity improvements, there may just be a mandate to use only AI supported languages in the office.

I think Elixir should find a way to be properly generated by AI tools lest organizations/developers will start using whatever language is most productive.

The question is: how much boilerplate code do you really write? Elixir compared to other languages has little to none boilerplate, and for moments such as phoenix things, there are configurable generators.

I wouldn’t want an AI incapable of problem solving to generate complex code for me, because as tempting as it seems, the productivity decreases a lot if we talk about refactoring generated code compared to creating your own new code.

Productivity is about solving a problem in the most efficient way, not about generating code the fastest, so I frankly don’t understand this argument.


You are giving both of these tools too much credit.

As @D4no0 mentioned, generating code just so you can get started with task X is not such a huge deal as people make it out to be. Emacs and VIM have had “snippet managers” for decades where you press a particular combo of keys and e.g. get a function with a for-loop over a list written for you.

GitHub Copilot and ChatGPT are better in that for sure – but not by much.

98% of all commercial programming is reading, understanding and modifying code. Improving the 2% that are the writing of the initial code is not impressive by any stretch of the imagination.

And finally, having something generate bigger scaffolds for you comes with the severe disadvantage that you might not understand that initial code and then you’ll lose more time first trying to understand it and then actually extending it or even using it on a basic level.


I’m wondering about this. I mean lot of time at least in our company’s software I first have to think about how to implement a feature because it might effect many places in the app. Lot of time is going into design then usually writing the code is just small part of the equation. It’s really hard for me to believe that 50% productivity claim from Copilot. I write TypeScript and I think it support that and maybe I’ll try it out.

Edit: It wasn’t 50% it was close to 30% source: Research: How GitHub Copilot helps improve developer productivity | The GitHub Blog


In my experience Copilot in elixir is pretty good. I’ve even found it to be better with elixir than with typescript.

1 Like

I agree, it will be mandatory that code can be generated by AI.
The fact that chatGPT is so much better - at a task it is not made for - than copilot lets us guess where Microsoft will go with it in the future. In a few years all code will be written in dialog with a bot, no loc will be entered by hand.

1 Like

And all progress will halt. Who is going to come up with new ideas then, the chatbot?

In this future I imagine it all eventually converges and every app ends up becoming a to-do app, styled using bootstrap, of course.


You’ll still have to think (for a while) and tell the bot what to do, what you want.

1 Like

They… Really aren’t. After two weeks of running Copilot on a JS codebase

  • it managed to suggest autocompletion maybe 5% of the time
  • maybe another 5% of the time it was actually useful or correct

All other cases IDEA’s autocompletion was better, and actually correct.

Both Copilot and ChatGPT are barely competent for the smallest and easiest of use cases. For the absolute vast majority of cases it’s a junior developer misunderstanding the assignment and spitting out some code that you have to thoroughly review to catch all the mistakes.

Don’t mistake raving reviews on Youtube/Twitter that are result of an early honeymoon period for actual usability of the products.


If you don’t want to work in a circus, don’t work for clowns.


For what tbh, AI code generation is currently garbage technology. You also mentioned ChatGPT as code generation AI / tool. It’s not. It’s a text generation AI and nothing else. Use correct tool for correct job and try not believing in stupid marketing phrases :smiley:


I think this is the same argument revolves about no-code solutions, a lot of solutions you build don’t have to be made from scratch and can be solved either at a higher level or by something that was already built, a simple example would be a system like node-red, because in most cases the defaults it provides are more than enough for you to get going.

Programming languages are for these fine grained requirements you have, where you can control everything starting from concurrency and ending with memory management, and in itself AI tool tries to abstract away having this fine grained control over the code.


We have an adage: “Do it slowly, I’m in a hurry”


They can’t “understand” code, even the one they generated.

ChatGPT is a generator. It’s not a refactoring tool.

All real code and projects must be refactored, even if only to add one small feature.


For those saying the code generated isn’t good quality or can’t refactor, or is only for boilerplate:

From Github:

Case in point: When we first launched GitHub Copilot for Individuals in June 2022, more than 27% of developers’ code files on average were generated by GitHub Copilot. Today, GitHub Copilot is behind an average of 46% of a developers’ code across all programming languages—and in Java, that number jumps to 61%.

It hasn’t even been out for a year yet. What will it be like in 2 years? 5 years?

And they just launched for businesses recently. It is coming!

We should at least make sure that Elixir is part of the generated code story. Otherwise we’ll have to debug python/javascript (or whatever language someone generated). I’d rather debug Elixir.

1 Like

This reminds me of these ads: “it clears 99% of all bacteria”.

Moreover there is this question about such tools, github copilot was trained on open-source code that is not all licensed to be operated on private projects, and this is applicable to all AI tools that steal data from random places.

1 Like

Right… everyone is like “Oh it’s like 95% correct.” So who’s going to debug the incorrect 5%?

Maybe there is some value in writing very consistent and predictable code, even if it’s not 100% correct, because the consistency/predictability is easier to debug.

But we ain’t there yet, so I’m gunna go sling some code tomorrow… :slight_smile:

1 Like

Just like me!

Seriously: all these “it produces bad code” arguments. Did you ever have to review code?

We will see what happens, I’m sure it will be disruptive.


Specific AI that would review your whole codebase and find all problems would be really helpful. I don’t think these generic ones will be proficient enough any time soon and my understanding co-pilot is not designed to that at all. Also having AI to understand concurrency to catch all those problems might not be a trivial task.
But one problem I see is that how can AI know the design spec to know in some cases something is actually wrong with your code. Because code could look like it’s working fine but according spec that is not included in the code something is wrong. I think this problem is much harder to crack than it looks from the surface.

1 Like

I assume you’re just being funny here because yes, professionally speaking you have to review and understand code much more than you have to write it.

Writing is the much easier part.

Nobody is stopping you from using these tools. By all means, go wild with them. We do have to warn you however: just having a bucket load of code you didn’t write – and it mostly works – will hurt you when you have to evolve it at one point. That’s all really.