I changed my view on traditional code review

> Review stops being a conversation about code and becomes evidence that certain properties hold.

> At that point it is hard to see what value there would be in saying that you would have preferred a for instead of a reduce(), or that a particular abstraction feels more elegant.

I'm sorry, I am still going to leave comments on bad code even if it "works". If it's not me, then its agents reviewing the diff for minimization opportunities along with best practices skills and checks.