[matsemann]

My use of AI is correct. My coworkers use is not.

I'm saying it in jest, but it's also a bit true. Not necessarily because we use it any differently. But because my use of AI saves me time. But their use of AI adds more to my plate, no matter if it's slop or not.

[Rumudiez]

I noticed very recently I actually prefer reviewing other people’s generated code over handwritten. There’s no ego involved and it usually does a better, more thorough job. We have enough infrastructure that by the time another human lays eyes on it for the first time each pull request has already been through 3+ rounds of automated review. Being the only specialist in my area on the team used to mean more coaching and more involvement in code review. Now my coworkers are sending me idiomatic solutions with modern approaches that I approve right away or with hardly any comments

[black3r]

So much this. When coding I use my LLM to hone the code to perfection before sending it to review, including running AI reviews on it multiple times and fixing obvious bugs so that reviewers have less work to do. I also test all my code manually (LLM can be helpful by giving me a list of test scenarios to consider). When reviewing PRs I carefully read the AI reviewer output, consider which points are relevant, which are irrelevant and only post the relevant issues when requesting changes.

I have coworkers who routinely post PRs with comments stating "all tests green, ready to review" and then I actually start the application, test it manually and it doesn't work. And don't get me started on reviewers who post the raw AI output of their "reviewing skill" and then I have to read through 30 paragraphs of "findings" most of which are irrelevant (just today I got the "valuable" feedback of "View is @api_view(["POST"]); no test asserts GET/PUT/PATCH/DELETE → 405")...