Hacker News Reader

Comment by XCSme | Hacker News Reader

This app[0] is entirely "vibe-coded", started on bolt.new which was like the OG way to vibe code and slowly improved over 1-2 years using various models.

I have no idea how the code looks like, and barely even tested the app entirely, because it is still not released yet, but I do think a lot about new features, tweaks, improvements, etc. Years of programming and game development did help, but I don't think anymore that code is relevant, as long as it looks ok and feels good.

[0]: https://ultimidi.com

View on HN

>not released yet

>barely even tested

So the lowest stakes possible and you have absolutely no idea what bugs are waiting.

Sort of, it's more of a heurisric of bugs found so far. There are very rarely any bugs, most of the changes I request are for tweaks/logic changes, not bug fixes. Usually things just work.

Also, I barely tested and kept changing things simply because of this: whatever I ask for, seems to work as expected.

You rarely find bugs if you rarely test the code.

It's a heurisric though.

It's one thing to test once and find 10 bugs, and another to test 10 times and find 1 bug.

> I have no idea how the code looks like, and barely even tested the app entirely, because it is still not released yet

This is worded as if knowing how the code works and testing it is hinged on it being released.

No, it was about testing only. I will only do a full test of the app when it's ready to be released, otherwise it makes no sense, as the app/product/flow still changes a lot. It's like prototyping a game, you try it a few times, see what's fun, what's not, and keep iterating. Only once you think it's good enough, you can start fully testing and polishing it.

Even after release, I don't see reasons to check the code if everything works and people are happy with the app.

Right, I missed that context that this was about your own app still in getting the idea right/prototype phase. I was talking more in general and would be quite concerned if with today's LLMs it was my bank/government backend system, handling my financials and personal data, written without no one ever looking at the code.

You know your app just immediately crashes to a blank screen the minute you enter a name, or finish a lesson right?

Firefox?

Firefox had an unsupported missing WebAudio. It should be fixed now, and I've updated my workflow to also test on Firefox. Let me know if the crash was in a different browser (not Firefox).

Reply on news.ycombinator.com