HN user
Just like calculators became crutches for school children memorising their times tables and our phones contacts list a crutch for memorising phone numbers, I see AI becoming a crutch for many, in all the areas we seem important and humanity has spent years refining (communication, thinking, writing, etc)
Ah yes, centralization.
I think thinking of code reviews along a scale might be beneficial here, if the two ends of that scale are "code review" and "feature review". A new hire, intern or any competent developer can look at some code, irrespective of context, and conduct a decent "code review", spotting problems in the code and aesthetic issues like you mentioned (spacing, misspelling etc).
A long time hire with experience on the code base would conduct more of a "feature review". Does the code address the problem or feature correctly? Is the code adhering to feature requirements? These are things that are answered towards the "feature review" of this code reviewing scale.
The thing is that code reviews are defined as a single action that encompasses that entire scale, making it so that regardless of experience or knowledge of the codebase, reviews by any developer is given the 'ok' once all issues have been resolved.
And this entire thing only applies to code reviews within organizations. Outside of those its even more of a wild west.
Gotcha, that was on the plan so appreciate it!