Pleasures and perils of Code Club

6
Pleasure and Perils of Code Club Some reflections on my 'first' Code Club, what it's like, what I'll probably do differently!

Transcript of Pleasures and perils of Code Club

Page 1: Pleasures and perils of Code Club

Pleasure and Perils of Code Club

Some reflections on my 'first' Code Club, what it's like, what I'll probably do differently!

Page 2: Pleasures and perils of Code Club

Background

Primary in Forest Gate, Newham Kids are probably wider age range than usual Started with 20 kids, now down to about 15 Opt-in, one hour at 3.30 on Monday Quite a few English as second language Not leafy suburb!

Page 3: Pleasures and perils of Code Club

Pleasures

Kids have fun, very open to new things Some very bright kids and some

'breakthroughs' Kids are staying, low drop out rate Some discussions 'non code club', partly

'pastoral/social' too Some exercises 'non code club' see

Computing at School: my 'robot drawing', for example

Page 4: Pleasures and perils of Code Club

Perils

Discipline, especially 'boys gaming' rather than coding

Very wide ability range in this club, hard to 'teach'

Can't do Code Club exercises in one go As a result, I'm preparing handouts/exercises Many problems with school IT [net speed/log

ons etc.] See above, saving and building on work

Page 5: Pleasures and perils of Code Club

Suggestions for 'new' year

Name badges, kids like badges Code club badges [anyway], perhaps by level Update and refine 'technique' handouts Lists of logons and passwords, always

forgotten Problem list for computers, Adobe updates etc. One or two opt-in 'big' projects

Page 6: Pleasures and perils of Code Club

Conclusion

Establish aims and expectations at start Need discussion with supervising teacher

about discipline/opt-in nature Not just extra child care/gaming time! Be prepared to 'fill in gaps'/CAS agenda Code Club size and effective support It's fun, do it, doubles size of IT access in

many cases too!