[shivaniShimpi_]

Every other field that's figured out high stakes failure models eventually landed on the same solution - make sure two people that understand the details are looking at it - pilots have copilots surgeons with checklists and nuclear plants have independent verification. Software was always the exception, cause when it broke it mostly just broke for you, vibe coding is not going to change the equation, it barely removes one check that existed before is that the people who wrote the code understood what was going on, but now that's gone too

[Ekaros]

We do have code reviews for pull requests. But on average I would guess there is great amount of complacency there. I suppose old proper QA phase was best answer we had. But that is expensive and slow.

[NoGravitas]

Maybe expensive and slow is actually an improvement.

[shivaniShimpi_]

i mean i don't disagree with you, but then there's at least unit test cases that we write as devs in a certain way that ai just doesn't understand quite well yet. we worked so much on speed that we forgot along the way that slow was a safety net. we tend to let our qa teams leverage ai as much as they want to automate test cases but i don't feel super comfortable getting rid of it just yet