Less programming,

more documenting. Seriously, the lack of proper documentation for a lot of fully-featured projects is absurd.

I agree.

or at least commenting, just one or two sentences in plain English saying what a function does (or in some cases, is supposed to do) would be nice.

A professor of mine rejected any programming assignment done without proper commenting. That should be mandatory in any CS course.

Like anyone is ever going to use some shitty CS assignment in their project. And if it's about forming good habits, then it doesn't seem to be working very well, at least in the open source realm.

>>4
Mine did that too, although he also encouraged stupid comments like //end of for-loop. Remember kids: Commenting is good, but commenting that ++i increases i is not helpful.