I agree with you.

> I think detractors believe you should just let AI do the job blindly instead of leveraging it as a tool to accelerate you.

However this is how it’s marketed. C-suite is telling people eventually you won’t need to read code, frontier labs saying programmers won’t exist etc.

The reality is like you said, a tool to accelerate you.

▲

user43928 5 hours ago | parent [-]

You can today develop a mobile app with 20 screens without ever reviewing any of the code generated.

If you test each feature and have it iterate on your feedback, you can build a decent product in this way.

Does it write too much code? Perhaps. Could I bring those 100k lines through code review in a team where some members nitpick? No.

That does not change the fact that it works, and that you do not need to read the code even today.

Unless progress slows down dramatically and soon, it seems rather likely that most of us will not be reading code in the near future. Their marketing is not wrong.

▲

overgard 3 hours ago | parent | next [-]

I really hope vibe coded apps have to be labeled as such so I can make sure to avoid using them. As a customer, I have zero interest in using something that was made with little care or expertise.

	▲	user43928 3 hours ago \| parent [-]
		If you think that the app I am working on suffers from little care or expertise, you would be mistaken. It works far better than the competition.

▲

skydhash 3 hours ago | parent | prev [-]

Unless the app is released and running on user’s device, your “it works” is on the level of hackathon’s demo. Being on prod has always been the true testing ground of code.

It seems like when people are talking about production level quality and how the AI. should be helping them there, plenty of people comes up with their “it works on my machine” anecdotes.

▲

user43928 3 hours ago | parent | next [-]

I use the app every day and I am confident in the quality.

I will launch it by the end of August. After ~4 months of hard work.

▲

cautiouscat 2 hours ago | parent [-]

If it’s 4 months of hard work, then it’s not like you’re blindly doing it as the top commenter mentioned.

▲

user43928 2 hours ago | parent [-]

That is true, I was mostly speaking about a supposed need to review the code.

My effort instead goes to manual QA testing, providing feedback and preferences, and asking questions.

The limitation here is mostly that the model does not know what looks and feels good.

With improvements to the vision capabilities and a better understanding of motion, or what looks appealing to humans, the implementation could probably happen much more autonomously.

	▲	skydhash an hour ago \| parent [-]
		> That is true, I was mostly speaking about a supposed need to review the code. Until you go to prod, you can believe a lot of things about the state of your code. Reviewing code is not merely about “Does this things work”. Testing and linting do cover most of that. Reviewing is mostly about: Will this design cover the current set of constraints (some may be conformance) and can it evolve? Are the assumptions correct? Is the security layer good enough?… The user interface part of the code is only one single component out of many.

▲

AussieWog93 2 hours ago | parent | prev [-]

Honestly, things have really changed in the past 6 months. Opus 4.5 got most of the way there, and Fable can now literally one-shot your run off the mill CRUD app.

I use a few of them daily. While there are still bugs, there are significantly less than there used to be back when everything was being maintained in my spare time.

Still not Netflix/Google standard yet, but definitely better than the average side project or pre-AI Bangalore special.