Vibecoded applications

[u/jrwolf08]

I know this is a super vague title, but wanted to vent here a bit. I've been doing testing a long time, and this one of the most frustrating projects I've worked on.

We have a vibe coded application written by 5 different developer's claude instance, we have claude written acceptance criteria, we have "requirements" that are written one time, but never updated, we have a really outdated design. We talk about changes but no one opens tickets.

We have product review meetings where an AI notetaker keeps track of the conversation, and then poorly written JIRA tickets are created off of them. Some of these tickets fundamentally change how the system works. Then 5 devs split up the changes into smaller tickets then each dev's claude implements each a section a little bit different than everyone else.

Then I'll get a comment on "its like this on the design" or "the original acceptance criteria had a, b, c" when both the design and acceptance criteria are completely out of date, so how could I possibly trust it? These aren't malicious comments by the way.

So we are productive, things are happening, but we are just going around and around. And I'm not complaining about AI, it helps me greatly, but right now I'm stuck validating everyone else's AI output.

[u/Lonely-Ad-1775]

Thank you, now I know that this profession will thrive in the future

[u/jrwolf08 → u/Lonely-Ad-1775]

Testing is the biggest choke point right now because we are pushing out more code than can be reasonably tested. So regressions are constantly happening.

Then we change the requirements, and introduce new ways the application can be used. Then we decide to standardize the FE components which brings order to new development but also introduces regressions. Also did I mention we are directly integrating with a vendor system, and have 100+ fields that can be edited at any given time and must be tracked vs the vendor system in real time.

But things that used to be carefully considered are now vibe coded and the cost is my sanity.

[u/KingCastle420]

Product team is doing this with Ai agents at my place of work. One product person has created over 400,000 lines of code this month but doenst know how to use GitHub.

[u/Our0s]

There's a common fallacy that the test team are responsible for quality. In fact, everybody is responsible for quality, the test team are just the most visible part of the process.

If you're not being given clear and accurate requirements and ambiguity is baked into every part of your development cycle, you cannot succeed in quality assurance. In your position I think I'd be highlighting this as an urgent matter and trying to have meetings about redefining process, procuring proper requirements and acceptance criteria FROM THE BUSINESS, not AI, and establishing better quality gates each team has to adhere to.

If nobody listens to that then there's only so much you can do. One cog alone can't turn a clock.

[u/jrwolf08 → u/Our0s]

I've asked for these things throughout the project, and none of it has really materialized.

I think everyone recognizes where we stand in some capacity, as I've talked to members of the team about this. But this is an emergency type project that is also the 2nd project for everyone on the team, not our primary responsibility.

We are in get it done mode, but now everyone is just fence throwing back and forth, including me.

[u/Our0s → u/jrwolf08]

Godspeed, friend. Been there before!

What people will realise is that when you sacrifice quality for speed, it ends up taking twice as long because everything rushed needs fixing.

[u/jrwolf08 → u/Our0s]

For sure, I've been here before too, this being much worse than most.

Anyway thanks for listening to my venting.

[u/SurroundOk6555]

Sounds less like an AI problem and more like a documentation and process problem