thanx for the tips and motivation. how long do you suggest a similar "workshop" should be? they are 3rd grade (8 yo) - the teachers told me that they could block the computer room for as long as I need - 1 hour or the entire morning... and they are 27 kids.
I was thinking about splitting the class in two groups for 2 hours each., but i am not so sure how much we could achieve in 2 hours..
I'm a web sysop and support engineer. My skills are mainly in back-end: Java, Linux, Python, PostgreSQL, Git, and GitLab. Currently I'm learning front-end skills: JavaScript, and Ruby.
The code club lessons are about an hour, which was all I had with a full class of 25+, and that felt about right for 10-year-olds. After that, you get some kids being bored and disruptive. You will be overwhelmed with that many on your own though! I had competent help from a teacher who knows how to control a class! So if your are going solo, I would say no more than about 8 to 10, in pairs sharing a computer.
So, if you can spare a whole morning, break them into groups, and do the same project with each group. You'll learn where the sticking points are. Also try a project out at home first, use your own kids as Guinea pigs, so that you can see what is difficult and be ready to fix technical issues so you can let the kids troubleshoot programming bugs, not issues with school wifi or saving to network shares.
thanx for the tips and motivation. how long do you suggest a similar "workshop" should be? they are 3rd grade (8 yo) - the teachers told me that they could block the computer room for as long as I need - 1 hour or the entire morning... and they are 27 kids.
I was thinking about splitting the class in two groups for 2 hours each., but i am not so sure how much we could achieve in 2 hours..
The code club lessons are about an hour, which was all I had with a full class of 25+, and that felt about right for 10-year-olds. After that, you get some kids being bored and disruptive. You will be overwhelmed with that many on your own though! I had competent help from a teacher who knows how to control a class! So if your are going solo, I would say no more than about 8 to 10, in pairs sharing a computer.
So, if you can spare a whole morning, break them into groups, and do the same project with each group. You'll learn where the sticking points are. Also try a project out at home first, use your own kids as Guinea pigs, so that you can see what is difficult and be ready to fix technical issues so you can let the kids troubleshoot programming bugs, not issues with school wifi or saving to network shares.
i will go solo. but my kid is already very excited about being my helper ( and therefore, somehow teaching his friends how to use scratch) :-)
thanx for all the advice!