Your code-review article is fascinating.
I wrote my first app in 1969, 64k of total memory, cards, and no regular reviews. One programmer did review my code and suggest better naming standards and comments. Even 4 years ago when I retired, I never went through many code reviews.
That first app ran for 18 years and never broke. It increased the company’s share of the market by 20%. IBM reversed a property on a datatype and they could not run it on new machines. The fix would have been simple, but they ran emulators of prior operating systems for years because nobody could understand or maintain it. They replaced it with a purchased app on a laptop.
They lost the documentation and underlying math books.
In my last job at age 65, they didn’t even have a test environment (until I got there).
As for code reviews, they are good for enforcing standards and forcing the programmer to think things through when presenting the new programs, just like teaching a class.
I don’t write code anymore, but I go through the same review process when I read my next article to my writers club and wait for the critiques (27 published book authors and me). My first one was a humbling experience.
Good points. By the way, bugs found after going into production is more expensive.
Besides, you might learn something reviewing somebody else’s code, like I did in a code review here: