Student challenges prof, wins right to post source code he wrote for course - Boing Boing - 0 views
-
Kyle's a student at San Jose State University who was threatened with a failing grade for posting the code he wrote for the course -- he wanted to make it available in the spirit of academic knowledge-sharing, and as code for potential future employers to review -- and when he refused, his prof flew into a fury and promised that in future, he would make a prohibition on posting your work (even after the course was finished) a condition of taking his course.
-
The most important lesson from it for me is that students want to produce meaningful output from their course-assignments, things that have intrinsic value apart from their usefulness for assessing their progress in the course. Profs -- including me, at times -- fall into the lazy trap of wanting to assign rotework that can be endlessly recycled as work for new students, a model that fails when the students treat their work as useful in and of itself and therefore worthy of making public for their peers and other interested parties who find them through search results, links, etc.
-
And in this case, it's especially poignant, since Kyle's workflow actually matches the practices of real-world programmers and academic computer scientists: coders look at one anothers' examples, use reference implementations, publish their code for review by peers. If you hired a programmer who insisted that none of her co-workers could see her work, you'd immediately fire her -- that's just not how software is written. Kyle's prof's idea of how computer programmers work is exactly what's meant by the pejorative sense of "academic" -- unrealistic, hidebound, and out-of-touch with reality. Bravo to Kyle for standing his ground!
- ...4 more annotations...