Indeed. The specific stuff you get at a code review depends completely on who else is on your team -- stuff that's great at one place is terrible at another. I

Indeed. The specific stuff you get at a code review depends completely on who else is on your team -- stuff that's great at one place is terrible at another. It's stuff you pick up from the specific software industry you join when you get out of school, web, embedded, desktop, whatever. The stuff you learn in school is useful for any of these, and is the same for all of them. Equally important, you can really tell who's been through those courses or not, independent of how well their code fits the normal maintainability or performance requirements. Higher-level concepts are just lost on them, or, if they've managed to pick some of it up informally, so intermangled with other conceptually-different topics that clear thinking and analysis is nearly impossible.