> If you know how to write clean code.

If we're assuming that:

I find it less time consuming to just write the code, understand it 99% (since I wrote it), and debug the rest, than it is to try to describe it to the AI, understand a fraction of what it spits out, and spend more time understanding it and fixing it.

If you can just write clean code just do that. Also, you will improve your skills even more the more you do that (shocker). So the next time you have to do that it will be even easier. This is called learning a skill.

Sorry for the rough tone, reading that back haha. But still posting because I'm just passionate about it, it's nothing personal though.

Reading is much faster than writing, that's a given. You can generate the rules in less than an hour, then never have to write a line of code again.

But maybe you have trouble writing prompts. Spend some time learning how to do that and it will be even easier. It's a skill ;)

Ash can be used in conjunction with Phoenix, they aren't mutually exclusive. Ash is really just a framework for modeling your domain(s) and getting a bunch of helpful functionality for free (e.g advanced querying capabilities, pagination, data validations, json+graphql apis, and more) Then you could use those functionalities with phoenix to build a full web app. Or you could use something else other than phoenix, it's up to you :)

OK HN, time for us to build a full open source general purpose ERP in Elixir based on Ash XD

"That's a great idea! Do you want me to create a PRD, a million markdown files and some useless Playwright tests?" -- Claude

... and you don't have token credits anymore.

AI Agents Assemble!