The trouble with objects?
(This post is a trackback to Knowing and Doing )
The above link makes for some interesting reading.
We have been arguing the very same point around here for a while now. Is Java (more specificly, OOP) being taught in first year serving our pedagogical interests and our students need? Or is it failing us and them?
I have approached the problem by trying to figure out what our true goal is. Are we here to teach programming or teach..what?
If our directive is to teach OOP, then we must find an effective way to teach objects, and while I do have a fondness for Java because it was the first programming language I realy learned, I'm not convinced it's the best way to teach objects.
Is our directive to teach Java? No it isn't, but then !
why do we use it? Beacuse it's a language used in industry and provides employability. Is that enough to base a curiculum on?
At it's core, I think our need is simply to teach programming. And we don't need objects for that.
But what, and how?
]]>