The imperative thing is so frustrating. Even the latest models still write elixir like a JS developer, checking nils, maybe_do_blah helper functions everywhere. 30 lines when 8 would do.
[flagged]
150k lines of vibe coded Elixir: The good, the bad and the ugly
41–50 of 91 posts
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#42Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#43The imperative thing is so frustrating. Even the latest models still write elixir like a JS developer, checking nils, maybe_do_blah helper functions everywhere. 30 lines when 8 would do.
Try these: - https://github.com/agoodway/.claude/blob/main/skills/elixir-... - https://github.com/agoodway/.claude/blob/main/agents/elixir-... - https://github.com/agoodway/.claude/blob/main/agents/elixir-... Getting pretty good results so far.
These should get added to https://skills.sh/?q=elixir
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#44Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#45Earlier quoted context omitted.
Which models are you using? I’ve had mixed luck with GPT 5.2.
Opus 4.5 with Elixir has been remarkably good for me. I've been writing Elixir in production since ~2018 and it continues to amaze me at the quality of code it produces. I've been tweaking my skills to avoid nested cases, better use of with/do to control flow, good contexts, etc.
I'll have to check it out. I've found GPT to be adequate at producing running code that I can improve either by hand, or very specific prompting.
What does your workflow look like?
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#46It's the second time today when I see that the higher number of LoC is served as something positive. I would put it strictly in "Ugly" category. I understand the business logic that says that as long as you can vibe code away from any problems, what's the point of even looking at the code.
Remember, there used to be a time programmers productivity was measured in LoC per hour.
As such, this is high productivity! /s
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#47I dont know erlang. My hobby LLM project is having it write a fully featured ERP in Erlang.
An ERP is practically an OS.
It now has
- pluggable modules with a core system - Users/Roles/ACLs/etc. - an event system (IE so we can roll up Sales Order journal entries into the G/L) - G/L, SO, AR, AP - rollback/retries on transactions
i havent written a line of code
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#48Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#49It's the second time today when I see that the higher number of LoC is served as something positive. I would put it strictly in "Ugly" category. I understand the business logic that says that as long as you can vibe code away from any problems, what's the point of even looking at the code.
[flagged]
'Means' according to what? Put some (laughtable) reference so I can laught louder.
Re: 150k lines of vibe coded Elixir: The good, the bad and the ugly
#50"It writes 100% of our code" - Silently closes the tab, and makes a remark to avoid given software at any cost.
You're not missing much. Seems to me like they wrote 150k lines of code for some glorified photo app with ChatGPT in the backend for image processing. Oh and some note-taking it seems.
I await (also doubt) the day this produces something truly useful and not just generic derivative functionality glued together