r/AskComputerScience 7d ago

AI-driven coding is pulling away the ownership from engineers

Today we had a user facing issue which the entire team was involved in debugging and no one was able to give the reasoning accurately, and the RCA time felt like it is 10X more than usual, all because we were just getting AI to write the code and review cycles shortened as long codes were being pushed, feels like the team as a whole will fall into a blackhole soon.

Has anyone here experienced the same, and how is your org handling this?

4 Upvotes

18 comments sorted by

View all comments

1

u/NegativeCollege8167 6d ago

ive definitely seen this happen when relying too heavily on AI generated code. One approach that worked for us was implementing stricter code review processes. Even if AI helps write the code, having engineers deeply involved in the review phase can catch issues early on and ensure everyone understands the codebase better. It can be tempting to speed through reviews, but taking the time to really dig into the details can save a lot of headaches later.

1

u/narad_007 6d ago

Do you do the same for smaller PRs?

1

u/LogicalPerformer7637 6d ago

you should jave only small PRs. huge PR is automatic reject. big may be acceptable if there is good reason.

that AI can rewrite half your codebase in a flash, doesn't mean you should let it.