ComputerScience

Jacob shares his top tips to running a fun and engaging Code Club

In February we met educator Jacob from Penpol School in Cornwall. He volunteered to join the Code Club panel as part of the Raspberry Pi educator sessions hosted in London. 

After the event, we caught up with Jacob and asked if he would contribute to our blog and share his experiences of running a fun and engaging Code Club.

Say hello to Jacob

Jacob has been running his Code Club at Penpol School in Cornwall for over three years.  He has a wealth of knowledge on running a Code Club. Let’s find out what his three tips are to running a fun and engaging club! 

Image shows teacher Jacob in his class room
Jacob from Penpol School in Cornwall

1. Have fun! 

Have fun with it. Running a Code Club is a fantastic chance to engage with students and children in a different way, everyone has come together to have fun and explore ideas with each other. The children have chosen to attend Code Club so they are already excited about the idea — take this energy and run with it! 

2. It isn’t a lesson 

Remember, it isn’t a ‘lesson’. This isn’t like a computing lesson in school, there is no set goal, no endpoint, no ‘finished!’ moment. Instead, children are encouraged to explore projects, take them in any direction they wish and discover new ideas and issues along the way. 

These moments provide excellent learning opportunities for both the children and yourself as they are real-world issues that they have encountered and want to explore, not scenarios you have planned in advance.

Young boy working at a computer
Code Club projects in action!

3. Embrace the dancing ice creams! 

Let the children lead the way. If they want to explore a certain set of resources, let them. If they want to change a project halfway through to incorporate a set of dancing ice creams, let them. They are learning, exploring, and problem-solving — whether in a structured or unstructured way. 

Don’t be afraid to let them take the lead and follow where they want to go.

Three girls sat in a line behind computers, smiling.
Learning to code with friends

You can follow Jacob’s adventures with code on Twitter, start a conversation, and share your Code Club experiences! 

What are your tips? 

What are your tips to running a fun and engaging Code Club? Let us know by tweeting us at Code Club UK & Code Club world using the hashtag #MyCodeClub 

Bug in the machine: six top tips for debugging your code

Making mistakes and learning how to solve them is a key part of becoming a coder. Read on to find out about the origins of the word ‘debugging’, and discover our newest resource to help your club members work through troublesome code. 

Programme Coordinator Zoe, holding the new debugging poster against a backdrop of an illustration of a house
Programme Coordinator Zoe, was excited to get her hands on our brand new debugging poster

Making mistakes is a part of learning 

The term ‘bug’ is used to describe a technical problem or mistake in code that stops it from working or behaving as you would expect. Every coder, from total beginners to seasoned experts, will have to deal with coding bugs, and it’s important to know the different approaches that you can take to fix them. 

‘Debugging’ is the term given to the process of working through your code to find and fix your mistake. Many things can cause bugs, from incorrect logic, to syntax errors, or even something as small as a missed comma. 

Bug in the machine 

The term ‘debugging’ is often attributed to U.S. Navy Rear Admiral Grace Hopper, a computer programming pioneer. In September 1947, Admiral Hopper was working with a team at Harvard on the Mark II computer, when they found an issue in one of the computer’s relays: a small, unobtrusive moth. As the moth was removed and taped into their research logbook, Admiral Hopper is said to have remarked that the team was ‘debugging’ the system. And so, the term was born — or so the story goes!

Whatever its initial origins, today, ‘debugging’ is a term used by programmers all over the world. 

Get debugging in your Code Club! 

We’ve created a new poster to help your Code Club members to debug their code. The poster explains what a bug is, and gives six top tips for Code Club members to try if they find a bug in their code: 

An image of the debugging poster, featuring spiders.
  • Check the project instructions — Have you followed the steps correctly? 
  • Read your code out loud — Does this highlight anything that is obviously wrong? 
  • Find the last time when your project worked — Can you isolate which part of your code is broken? 
  • Show your Code Club leader — Can your club leader help find which bit of your code isn’t working? 
  • Ask a friend — Get another pair of eyes to check your code! 
  • Stay calm and keep trying new things — The most important thing is to not get frustrated; you’ll find your bug if you keep looking! 

If you’re based in the UK, the USA, or Ireland, head to your dashboard to download your copy of our debugging poster. 

If you’re based outside of the UK, the USA, or Ireland, head to our Code Club international website to download this poster and other resources.