close

Discovered in

sheaman42

sheaman42
40K Favs
Recently online

Find other sites about

Related Sites

  • Student challenges prof, wins right to post source code he wrote for course - Boing Boing

    Kyle Brady writes, "Thanks to some perseverance and asking the right questions, SJSU professors are now prohibited from barring students from posting their code solutions online, as well as penalizing their students for doing so. A win for students, programmers, and copyfighters... more

    Reviewed by sheaman42 Jun 11, 04:48am ( 12 reviews ) • boingboing.net

    25K views
  • Showing 5 of 12
  • Reviews of the site
  • Join StumbleUpon or login to add a review! default avatar

  • Reviewed by testnow1980 on Aug 19, 6:07am

    http://www.code-microsoft.com

  • Reviewed by isatcjk on Jun 13, 8:51am

    From the page: "There's a lot of meat on the bones of this story. 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. But the convenience of profs must be secondary to the pedagogical value of the university experience -- especially now, with universities ratcheting up their tuition fees and trying to justify an education that can put students into debt for the majority of their working lives. Students work harder when the work is meaningful, when it has value other than as a yardstick for measuring their comprehension. I've always thought it was miserable that we take the supposed best and brightest in society, charge them up to $60,000 a year in fees, then put them to work for four years on producing busywork that no one -- not them, not their profs, not other scholars -- actually wants to read. Might as well get them to spend four years carving detailed models of ships from sweet potatoes (and then bury the potatoes). "

  • Reviewed by SMA11784 on Jun 11, 1:15pm

    I'm guessing PurposefulStride here is a bitter university professor, pedantic and hostile.

  • Rated by PurposefulStride on Jun 11, 7:57am

    Interesting, but the article is _very_ poorly written--distractingly so: "and [available] as code for potential future employers to review;" "he would [/s]make a prohibition[/s]prohibit students from posting their work [s]on posting your work[/s];" "and that [??] Dr. Beeson cannot claim otherwise" (is that really what they wrote?); "[For me,] the most important lesson from it [s]for me[\s];" "from their course-assignments" shouldn't be hyphenated; "rotework" not a word; "endlessly recycled as work for new students, a model that fails when the students ..." run-on sentence; "But the convenience of profs must be secondary..." I think he means "The professors' conveniences must be secondary;" "put students into debt for the majority of their working lives..." I don't think anyone argues that student loans put the average student in debt for >22.5 years; "I've always thought it was miserable that we take the supposed best and brightest in society...put them to work for four years on producing busywork that no one...actually wants to read" this is just my opinion, but if no one wants to read the students' work, they are not the best and the brightest; "...implementations, [and] publish...;" "none of [his or] her co-workers" there's on point in pretending; etc.

  • Rated by sheaman42 on Jun 11, 4:48am

    Kyle Brady writes, "Thanks to some perseverance and asking the right questions, SJSU professors are now prohibited from barring students from posting their code solutions online, as well as penalizing their students for doing so. A win for students, programmers, and copyfighters nationwide!" 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. Kyle appealed it to the department head, who took it up with the Office of Student Conduct and Ethical Development and the Judicial Affairs Officer of SJSU, who ruled that, "what you [Kyle] have done does not in any way constitute a violation of the University Academic Integrity Policy, and that Dr. Beeson cannot claim otherwise."