WOW, Lines of Code. I remember that, back in the day. Never used it, though. I got the feeling it was something done by consultants in order to pad their cost estimates for negotiating contracts. ("That will take somewhere in the neighborhood of 25K lines of code to write, at a cost of …") I'm glad that's gone.
Unfortunately for me, although I've been in the industry of writing code professionally for many years, I've never sat in on any code reviews. Maybe its the area I live in; no body wants to do them. I think it would be a good idea and like the blog post you linked to, Steve, we do spend a lot of time reviewing others code or our own code written years before. ("What idiot wrote this piece of crap? Oh, it was me.")
On the other hand I have been on teams working on code. Its been a mixed bag. I've worked with other developers who are lone wolves; they don't, under any circumstances, what to work with anyone. So, it's a team in name only. But by and large I'd say most teams I'm on have been positive experiences. I'm on a team now with one other guy. We Skype a lot (he's hundreds of miles away from me, so that's how we have to communicate). I get along with him and when one of us have other demands, the other can pick up the slack. Yeah, I'd say that teams are, for the most part, great.
Kindest Regards, Rod Connect with me on LinkedIn.