Pretty much all CS departments don't want solutions for most assignments (open-ended final projects excepted) on GitHub for a simple reason: they reuse assignme

Pretty much all CS departments don't want solutions for most assignments (open-ended final projects excepted) on GitHub for a simple reason: they reuse assignments term to term because it is incredibly difficult and work-intensive to develop an excellent CS assignment. While it might be possible in some courses, in many, it would be impossible to develop new assignments every term at the quality that they currently use now. While most schools do employ quite good plagiarism detection technology (eg. MOSS) that will catch if someone turns in an assignment done by a previous student, they'd rather not have to report multiple students every term to judicial affairs, and they can't catch smaller academic dishonesty like looking at others' code to get ideas for design decisions. For example, the Operating Systems assignments I did in university[1] are spectacular. The starter code is great, they're intense, they don't make you waste time on stuff that's not too educational. I learned a ton from them. They've been in use for years, done by probably thousands of students, and there would be no easy way to seriously change them yearly. I'm very glad my professors were able to invest in developing a great assignment set once and then reuse it year to year. 1: http://www.stanford.edu/class/cs140/projects/pintos/pintos_1.html http://www.stanford.edu/class/cs140/projects/pintos/pintos_1...