Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Prof Questions Sink-or-Swim Intro to CS Courses 2

Submitted by theodp
theodp (442580) writes "'After having taught introductory programming (CS 1) for the past six years,' writes GVSU's Zack Kurmas, 'and having watched many students struggle through this course and the subsequent course (CS 2), I have come to the conclusion that it is absurd to expect students who don't have any prior programming experience to be well prepared to study Computer Science after a single 15-week course (i.e., CS 1). I believe that expecting a student to learn to program well enough to study Computer Science in a single 15-week course is almost as absurd as expecting a student with no instrumental musical experience to be ready to join the university orchestra after 15 weeks.' Kurmas' frustrations are not unlike those voiced by Physics prof Dr. Yung Tae Kim, who argues the up-or-out, one-size-fits-all rigid pace approach to learning set by teachers and administrators is as absurd as telling a toddler, 'You have ten weeks to walk, and if you can't, you get an F and you're not allowed to try to walk anymore.'"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Prof Questions Sink-or-Swim Intro to CS Courses

Comments Filter:
  • From what i remember reading, America has been on a downhill slide in education for the better part of 10 years... I think this just shows that University admins have no clue how to properly educate our growing out of place workforce.
  • It's perfectly reasonable to say that people won't program well after 15 weeks, but what he's proposing, making students wait a year before really doing any serious writing of programs, would be disastrous. Personally, I remember feeling somewhat impatient with the speed of my own introductory programming classes; I couldn't imagine having had to wait even longer before programming. And so you might produce bad code; the act of programming itself forces you to think computationally and is really the best le

"No job too big; no fee too big!" -- Dr. Peter Venkman, "Ghost-busters"