As a senior engineer, I am getting extremely tired of reviewing AI slops. Today at work I have decided that I just have to build a POC project from scratch. I spent 2 weeks to review the code, to log the process, and to build toy examples to make my argument clear that some (actually most) parts were not working.
The funny thing is that I know my manager got this “working” within a week with Claude. I had to spend 2 weeks with 4 JIRA tasks, many commits for toy examples, and three reports.
I'm afraid the only options are to stop, give pushback, or embrace it yourself and use AI to review - just add the caveat that "since you decided to not put in the effort, neither will I". Just make sure the author is on-call for outages.
why is there even an expectation / requirement that a POC's code should be taken into production? wouldn't you be much faster to just regenerate from scratch, but this time with your proper architectural guidelines in a planning document and with proper code reviews in place?
I feel often codes from a manger do not go through rigorous code review process, especially if it is a POC. In my case, because of 1 to 10 signal to ratio, it was hard to pin point which parts actually did the jobs done. I am setting things properly this time, me as a maintainer. Thanks for commenting.
Reading this, honestly, I'd say the problem is you then?
Velocity is everything.
This is something even my manager wouldn’t say. I think he is feeling embarrassed from all the evidences. To be fair you didn’t read them. I agree that velocity is everything and as a manager they shouldn’t slow the team down.
I don't know what your evidence is, but I'm fairly sure I'm on the polar opposite. I see it working and it's the new norm.