« Installing the Allegro Library under DevC++ | Home | Turn Off Those Lights! »
A Response to ‘Learning Before Learning’
I recently came across a guest post on the CompSci.ca blog that discussed the merits of learning, or exposing yourself to material before it is studied in your school’s computer science curriculum: or, working ahead. This issue isn’t as hotly debated as you would think, but there are very strong arguments to be made on both sides.
Working ahead in a competitive CS curriculum can be harmful. You, without the guidance of an instructor, run the risk of learning things wrong. It is possible to get the wrong idea about things and how they should be used; things such as subtle optimizations, and improvements may be overlooked by a student ’studying’ ahead. In my experience, trying to nail down important coding ideas is troublesome without some guidance. I can’t say that I speak for everyone, but for me, getting involved in a class with a knowledgeable instructor improved my coding ability far greater than I could have on my own – comparing notes is important. I walked into the classroom thinking I knew what I was doing, but I walked out with the knowing of what I was doing wrong.
I’d have to say that the merits of working ahead depend solely on the student involved. If we have a student that has been coding solo for a while, we can safely assume that working ahead would probably be beneficial to this student. However, a student with little no no experience should probably choose to stick to the pace of the class - at least when starting out. The article above mentioned that students should learn at their own pace, and I wholeheartedly agree with that sentiment. So it’s important for a responsible student to figure out where they stand in terms of what you know and don’t know, and then make an informed decision on what would most benefit their education.
I didn’t have the opportunity to ’skip class’ in high school in order to focus on working ahead like some do in college. This practice is a bit dodgy at best. As stated in an earlier paragraph, missing out on an important tidbit of any sort is debilitating. a responsible programmer should be on the lookout for any bit of advice that would allow him/her to improve upon some aspect of his/her code. Heck, I know I am.
To put it shortly, or at least somewhat shortly, working ahead is fine as long as you are comfortable doing so. Learning at your own pace is a fantastic, but you shouldn’t completely forget about the lesson that is going on right now. Use your free time to work ahead, not your class time.
Outside of the classroom is a different story entirely – but I suppose I could save that for another article.
Similar Posts:
About this entry
You’re currently reading “A Response to ‘Learning Before Learning’,” an entry on The Angry Walrus
- Published:
- Jul 26 2008 / 9:04 pm
- Category:
- Programming, Response, School
Comments are closed
Comments are currently closed on this entry.