$msg = ""; $myaddress = "sacha" + "@" + "sachachua.com"; $page = "2003.06.06.php"; $page_title = "2003.06.06"; $page_updated = "2004-11-2106:44:1306:44:13-0500"; $maintainer = "sacha" + "@" + "sachachua.com"; require_once "include/calendar.php"; require_once "include/planner-include.php"; require_once "include/header.inc.php"; ?>
What elements of student-centered learning did you observe in this lesson/presentation?
What worked? What could be improved?
What other aspects of SCL may be added/included?
Repeated student answers and worked them into the discussion.
Two days worth of lessons; conceptual framework, and the first lesson. Typical history lesson: what is the basis of history? Man is a temporal being. But before you can understand that, you have to ask "who are you?"
Homo sapiens Dom. What's Dom like? (Aside from being a Homo sapiens). Filipino, 21 years old. Chemist. Love science. Love teaching science.
Answers from his past dictate who he is now, and who he is now shapes his future. We tend to look at time in three discrete blocks, but they interact.
Unconventional examples. =)
|A1||X||Fix yatm.el for enabled/disabled|
|A2||X||Find out why custom has a problem; see if it's still in CVS|
|A3||X||Find out why planner lost fontlocking!. To be precise: the faces - maybe my Emacs' fault? Emacs' fault. Yeah, I was using a fixed font that didn't have bold or itals; silly me.|
But when you think about it, that doesn't really work out. Sure, there are short-term benefits - people solve their problems quickly and stop asking you, and they go away impressed by your knowledge - but long-term, this just sucks. To be precise: other people become more reliant on you or on other gurus. They don't have the opportunity to develop their own skills and learn how to learn. They also come to see computer science as something they can't do on their own - something that they'll always need help with.
I don't know when my mindset shifted, but I found myself starting to ask questions instead of giving answers. I'd help people break their questions and problems down into smaller problems that they already knew how to solve. I'd point them to documentation that might be useful and help them understand the trickier parts. Although this approach initially frustrates people who just want an answer fast, I feel that this is, indeed, the only way to help them grow. Breaking problems down and helping them recognize the subproblems they can solve boosts their confidence while developing their problem-solving skills. Asking them questions challenges them to think.
If we always spoonfeed people, we risk making them dependent on us, and we are partly responsible for their inability to eat on their own. It's something to think about, isn't it? When you're taking care of babies, of course you don't give them solid food right away. You give easily processed food in small portions - a little bit at a time, so that they get used to it. However, they can't be spoonfed forever. You start introducing solid food in small bites. Then you teach them how to feed themselves - how to use a spoon, how to use a fork, and even how to use a knife to cut their own meat. Eventually they'll even figure out how to cook their own food. Some will even create entirely new recipes! Isn't that cool? =)
Besides, one has to keep in mind the reason why people ask questions. Is it a homework question? If they're doing it as part of a class, then the teacher would expect them to have done significant work. If you just give them the answers, then you're helping them deprive themselves of a good education. ;)