Code reviews are like threat models or unit tests: checking a box. People come to the meeting straight from the printer and are seeing the code for the first time. They quibble over formatting and consistency.

I usually worked on servers where memory was allocated in processing a request, so each time one came in I created a custom heap, did all my allocation for the request out of it, then freed the entire heap at the end without bothering freeing the individual allocations.

I started with servers that had to be restarted every four hours to recapture leaked memory and turned out servers that never leaked a single byte.

It takes a long time to write a big project in C but at least you can see everything but the stack operations, right in front of you. The JavaScript I am working on now bears no discernible relation to the page it implements, I can't even find where a checkbox or a button is coded. I hate browser work.