I'm seeing amount of changes needed to produce new features when coding with these AI tools constantly increasing, due to the absence of a proper foundation, and due to the willingness of people to accept it, with the idea that 'we can change it quickly'.
It has become acceptable to push those changes in a PR and present them as your own, filled with filler comments that are instant tech debt, because they just repeat the code.
And while I actually don't care who writes the code, I do expect the PR author to properly understand the code and most importantly, the impact on the codebase.
In my role as a mentor I now spend a lot of time looking at things written and wonder: Did the author write this, or did they AI? Because if the code is wrong, this question changes how the conversation goes.
It also impacts the kind of energy I'm willing to put in into educating the other person as to how things can be improved.
Which is a great idea until your superior asks why you're holding back the vibe coders and crippling their 100x productivity by rejecting their PRs instead of just going with the flow.
I'm seeing amount of changes needed to produce new features when coding with these AI tools constantly increasing, due to the absence of a proper foundation, and due to the willingness of people to accept it, with the idea that 'we can change it quickly'.
It has become acceptable to push those changes in a PR and present them as your own, filled with filler comments that are instant tech debt, because they just repeat the code.
And while I actually don't care who writes the code, I do expect the PR author to properly understand the code and most importantly, the impact on the codebase.
In my role as a mentor I now spend a lot of time looking at things written and wonder: Did the author write this, or did they AI? Because if the code is wrong, this question changes how the conversation goes.
It also impacts the kind of energy I'm willing to put in into educating the other person as to how things can be improved.