The latest articles on DEV Community by John from BoothIQ (@john_boothiq). https://dev.to/john_boothiq https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3798789%2F62262d13-517a-40ec-9a93-ff4268dbe44a.png https://dev.to/john_boothiq en John from BoothIQ Sat, 28 Feb 2026 19:52:56 +0000 https://dev.to/john_boothiq/150000-lines-of-vibe-coded-elixir-the-good-the-bad-and-the-ugly-1e1o https://dev.to/john_boothiq/150000-lines-of-vibe-coded-elixir-the-good-the-bad-and-the-ugly-1e1o <p><a href="https://getboothiq.com/blog/150k-lines-vibe-coded-elixir-good-bad-ugly" rel="noopener noreferrer">Reflections on 6 months of AI-Native Development</a></p> <p>TL;DR:</p> <ul> <li>Good: AI is great at Elixir. It gets better as your codebase grows.</li> <li>Bad: It defaults to defensive, imperative code. You need to be strict about what good Elixir looks like.</li> <li>Ugly: It can’t debug concurrent test failures. It doesn’t understand that each test runs in an isolated transaction, or that processes have independent lifecycles. It spirals until you step in.</li> <li>Bottom Line: Even with the drawbacks, the productivity gains are off the charts. I expect it will only get better.</li> </ul> ai productivity softwaredevelopment vibecoding