> I only had one CS project in my senior year that involved building something with another person and even in that case it was only one other person. I had ma

> I only had one CS project in my senior year that involved building something with another person and even in that case it was only one other person. I had many group projects in school, but they didn't set it up so that we'd review each other's code. We'd just break it up into modules, split the work accordingly, and each worked on a different part. A more fundamental limitation of school projects is that they have by definition a limited lifespan, so that the notion of code debt, the importance of ensuring that code be readable by current and future colleagues, etc. are irrelevant - in all the projects I've done in school, even group ones, I was the only one reading my own code and it would never be run after class finished. In such a situation, "improve overall code health" makes no sense. You write only what you need to pass the class, which is usually some kind of demo feature. Maybe making contributions to well-established open source projects should be encouraged as part of the curriculum, at least to experience the receiving end of it...