I reviewed some code that was also reviewed by
Coderabbit dot A.I.. It claims:
Cut Code Review Time & Bugs in Half. Instantly.
So, it fills your pull request with stuff like this:
According to the coding guidelines, API-related functions should be reusable methods that can be used both in ____ and elsewhere. Consider exporting the _____ function to enable reuse in other contexts.
Yes, statistically, comments about exporting functions will often near text about code reuse, and quite possibly, the client told it they wanted to maximize code reuse. It slapped this comment on several functions, and there was nothing particularly reuse-worthy about any of the functions.
How would this go for the company wanting to cut code review time in half? They probably would drop a lot of code review time. But then they would have to review a lot of comments like this, many of which would take longer to debunk that this one. It's the same situation as
snyk's false positive machine.
An even worse scenario is the case in which the developer is new and is hoping to learn from A.I. They'd probably just take away from this that `export` should go before every instance of `function` in this case, and probably pick up more harmful misconceptions elsewhere.