Studiot said:
Chiro, I really don't have a clue what you mean.
I would also venture that you don't have much idea of what I was talking about, given your response.
Do you have first hand experience of the events I described?
Please all let's remember the original question was
When should calculators be introduced?
not
should calculators be introduced?
I've already given my own response to that earlier in the thread, but in case you were wondering, my response was give them calculators when they understand the processes used on their calculators.
My later response though was targeted specifically at your response for programming, not for the calculator debate and I thought this would be crystal clear given that your response focused on programming.
All I'm saying is understanding programming, much like understanding mathematics is not about understanding a specific language or a bunch of largely un-connected specific examples like we have in the high school curriculum (right angled triangles, angle classifications for straight lines, etc).
Instead real understanding comes from knowing constructs like for example, doing a loop so many times to calculate a polynomial expression, or using an if statement to decide whether to use option a or optio b.
These kinds of things don't depend on languages in the absolute sense and if its taught this way, then the students will not be learning and we will continue the stupidity that is already happening in the classroom, where the students typically know the answers, but they really don't actually understand that much.
I don't have first hand experience of students being introduced to programming in schools on a classroom or school level, but I have helped a variety of people to learn programming of various backgrounds and ages, and I have seen that the learning difficulty shares similarities in mathematics where people often just do things without knowing until suddenly the lights go on and it makes sense.
In some of the above situations, people just read code (or reading symbols in mathematics) and they don't fully know what the code is even doing, so they fudge the code in some way to try and get what they are aiming for until it magically works.
This situation can be amplified when you use specific implementations and examples and if the course is structured bad enough, students can get away with going through the whole course by using a kind of superficial understanding to know what to fudge even if they have no clue why.
This is the gist of what I was trying to get at.