AI Coding Agents Changed What I Review in ML Apps
For a while, my workflow for building ML applications with coding agents looked something like this:
Write a prompt.
Wait for the agent to make changes.
Open the diff.
Read the code.
Try to understand what changed.
Run it.
At the beginning, this worked surprisingly well.
The changes were small, the codebase was familiar, and I could still keep the whole thing in my head.
Then the application grew.
A seemingly simple feature could now involve preprocessing, model inference, postprocessing, and application logic.
The agent might touch several modules and add a few hundred lines of code in a single session.
My habit didn’t change.
I was still reviewing the code after every session.
And that became the problem.
The code review trap
When a coding agent changes a few lines of code, reviewing the diff is easy.
When it changes several hundred lines, it is still manageable.
Once you...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
