Hold the submitter to a higher standard by introducing penalties for errors, and/or incentives for clean PRs. In my opinion a PR should be flawless once submitted, as the dev should have tested thoroughly. QA should only catch errors in a small percentage of cases
By slowing down engineers with ai agents adding multiple code reviews on top. Also encouraging engineers to engage in manual testing themselves to better understand the product.
Hold the submitter to a higher standard by introducing penalties for errors, and/or incentives for clean PRs. In my opinion a PR should be flawless once submitted, as the dev should have tested thoroughly. QA should only catch errors in a small percentage of cases
By slowing down engineers with ai agents adding multiple code reviews on top. Also encouraging engineers to engage in manual testing themselves to better understand the product.
Making PRs faster doesn’t help much if QA is still slow.....it just moves the problem to QA.
You guys have QA?
[flagged]
[flagged]
[dead]
[flagged]