logoalt Hacker News

cpursley • today at 5:52 AM • 5 replies • view on HN

It’s a shame that the LLMs default to Next when vibe coding instead of something serious like Phoenix. Then again, maybe it’s a good thing - all of the sloppy copies of my saas are complete dumpster fires and only going to slow them down.


Replies

desireco42 • today at 5:59 AM

Shame but also opportunity... These apps will not be good, they will look good and appear to work, but then... they will need to be rewritten.

I am often posting that if you pick Gleam for UI, Rails or Phoenix, which will make your codebase easier to follow and more stable, I will give you discounts.

➕ show 1 reply
sergiotapia • today at 5:56 AM

Have faith, you can be the change you want to see.

At my new job we needed a robust platform for executives and ops people to vibe code in. I created the project using latest Phoenix and everything works flawlessly. We get so much for free, hosting is peanuts, and iterating is easy for the AIs.

I even have tons of really strong deterministic guardrails for people vibecoding:

    Before you commit, run mix precommit and make sure it's green.
And mix precommit is:

    precommit: [
      "compile --warnings-as-errors",
      "deps.unlock --unused",
      "format",
      "credo --strict",
      "ex_dna",
      "reach.check --arch",
      "dialyzer",
      "test"
    ]
Credo has https://github.com/elixir-vibe/ex_slop added to it.

It's really great, try it out.

➕ show 1 reply
yipinwong • today at 6:44 AM

[flagged]