|
|
|
|
|
by catcontent
1997 days ago
|
|
maybe this is just an outlier experience, but I deny that teaching (like telling somebody how to do something) is a successful approach at all.
a widely underestimated ressource is that the learner wants to learn it. so, the best you can do is to show your owh profit from programming. then wait for questions. and I mean wait.
I have seen intelligent parents push their kids and really getting them annoyed and thus unwilling to learn stuff. very good for questions you can not answer yourself is
https://zen.coderdojo.com/find
here, kids can (but don't have to) work on their own projects, ask highly qualified experts and -- even more importantly -- watch other kids working on their projects.
plus: I have seen 6 year old kids presenting their project to 150 people at the coderdojo without even realizing what skill they acquired. it boils down to 3 aspects:
Mastery, Autonomy and Purpose from my "teaching experience" with adults, giving the responsability to the learner is the important part.
I hold seminars starting with an empty document. then I ask people to ask questions, otherwise the seminar would be over within the next 10 minutes. people instantly wake up and start to take responsability. |
|