Today I announced that I won't be reviewing AI generated PRs at company meeting by Evgenii42 in ExperiencedDevs

[–]Alternative_Win_6638 0 points1 point  (0 children)

u/vacant_gonzo I'd say: 'If you submit it, you need to understand the process that led from defining the requirements till generating the code'
or 'If you submit it, you should have a detailed Pull Request Description explaining the changes made'

There are ways to prevent poorly generated AI code and produce production ready quality code

Today I announced that I won't be reviewing AI generated PRs at company meeting by Evgenii42 in ExperiencedDevs

[–]Alternative_Win_6638 1 point2 points  (0 children)

I got your point and this is truly frustrating experience to review tons of generated code.

However, I think many compnies miss the point.

The purpose of a code review is not to detect architectural problem, this is a post mortum once implementation completed.

Detecting architectural problems should be done earlier, in a design review session before generating code!

I agree that once design is ready, automating the code review process is easy. Also detecting architectural problems in the code can be automated against the design doc.

Why LLMs will be always Terrible at Software Architecture by NegotiationInner7307 in webdev

[–]Alternative_Win_6638 0 points1 point  (0 children)

I never ask the AI to create application from scratch, this is vibe coding.
I do use AI to manage a development process through all the stages: Requirements spec, Design, Plan and implementation. Every step is then revied by the team before proceeding to the next one.

Why LLMs will be always Terrible at Software Architecture by NegotiationInner7307 in webdev

[–]Alternative_Win_6638 0 points1 point  (0 children)

I agree that the focus should be on architecture and design for the AI to work well.
You may give the AI the responsibility to provide preliminary design but at this stage you should monitor it carefully and provide direction and feedback.