STR Coding Club logo STR Coding ClubLearn to code, together
Club Projects

Coding Club Demo Day Ideas That Beginners Actually Enjoy

Ask a room of first-year coders whether they want to show their project to everyone, and roughly two thirds will look at the floor.

Young coders at tables showing their projects on laptops to small groups of visitors

Ask a room of first-year coders whether they want to show their project to everyone, and roughly two thirds will look at the floor. Ask the same group six weeks later, after a well-run demo day, and most of them will ask when the next one is. The difference is not confidence. It is format.

A coding club demo day is the session where members show what they built, usually at the end of a project cycle. Done badly, it is a queue of nervous people apologising for bugs in front of a projector. Done well, it is the session your club remembers all term. I have run fourteen of these with groups aged eleven to sixty, and these are the parts that make the difference.

Decide What a Coding Club Demo Day Is For

Before you book the room, settle one question: is this a celebration or an assessment? Clubs that mix the two get the worst of both. Members spend the week dreading judgement, and the session feels like an exam.

For beginners, make it a celebration. Nobody scores the projects, nobody ranks them, and nobody wins a prize for the best one. The goal is that every member explains one thing they made work and one thing they learned when it did not. That framing changes what people bring. Instead of hiding a half-finished quiz game, they show it and explain why the scoring loop broke.

Pick a Format That Fits Your Room

The default format, one person at the front while everyone watches, is the hardest for beginners and the slowest for the club. With twenty members at five minutes each, plus setup, you lose nearly two hours. Here are three alternatives I have used:

FormatBest forTime for 20 members
Science fair tablesNervous beginners, mixed ages45 to 60 minutes
Lightning demos, 2 minutes eachConfident groups, short sessionsAbout 60 minutes
Pairs presenting togetherGroup projects, shy membersAbout 50 minutes

Science fair tables work best for most first demo days. Each member or pair sits at a laptop, visitors walk round in small groups, and the same explanation gets given five or six times to three people at a time. By the fourth round, the quietest coder in the room is explaining their list sorting to a parent with real pride.

Give Everyone the Same Three Prompts

Beginners freeze when told to "present your project". They do much better with a script. Print these three prompts on a card at each table:

  1. What does your program do? Show it running.
  2. Which part was hardest, and how did you get past it?
  3. What would you add with one more week?

The second prompt is the one that matters. It turns bugs into stories. A member who spent two sessions stuck on an off-by-one error in a loop has a genuinely interesting thing to say, and other beginners recognise themselves in it.

The Advice to Only Show Finished Projects

A lot of club guides say demo day should only feature working, polished projects, so that members feel proud and visitors are impressed. I disagree, at least for beginner groups.

If only finished projects get shown, the members who struggled most either stay home or stand at the back. Those are exactly the people a club is trying to keep. Allow a "work in progress" label on any table. In my experience about a third of beginner projects are not finished on demo day, and the conversations at those tables are often the best in the room, because visitors start suggesting fixes.

The one rule I do keep: something must run. Even if it is only the first screen of a text adventure, there should be something to see on the laptop, not just code.

Prepare the Tech the Week Before

Most demo day disasters are technical and avoidable. Run a ten minute check in the session before:

  • Every project runs on the laptop that will be used on the day, not just at home.
  • Any files the program reads, such as a saved scores file or a word list, are in the right folder.
  • Projects that need the internet have an offline fallback or a short screen recording.
  • Font size in the editor and terminal is at least 18 so visitors can read it standing up.

The last point sounds small. It is the single change that most improves how projects come across, because people can finally read what the code says. If your club follows a structured cycle like the one in how to plan a six week coding club project beginners finish, put this check into week five.

Turn Visitors Into Useful Feedback

Parents, friends and other club members will want to say something nice, and "that's cool" helps nobody improve. Hand every visitor a small stack of sticky notes and ask for one specific note per table: one thing they liked and one question they still have.

Collect the notes at the end and give them to each member. Questions such as "what happens if two players get the same score?" are more useful than any praise, and they often become the next project. For how to shape comments beginners can actually act on, see code feedback beginners actually use and remember.

Keep the club leads in the background

Mentors should circulate, not stand at tables. If a mentor explains a member's code for them, the member learns that their own explanation was not good enough.

FAQ

How often should a coding club run a demo day?

Once per project cycle, which for most clubs means every six to eight weeks. More often than that and members spend too much time preparing to show rather than building.

Should we invite parents and outsiders?

For the first demo day, keep it to club members and maybe one guest each. Once members have done it once, opening the doors wider works well and helps recruit new members.

What if a member refuses to take part?

Let them pair with someone or help run the timer. Most reluctant members join in the next time once they have seen that nobody gets judged.

Run Your First One Small

Book an hour, use science fair tables, print the three prompts, check every laptop the week before and hand out sticky notes at the door. Allow unfinished work and insist that something runs. After the first one, ask members what to change, because they will tell you exactly what made them nervous. For more project ideas to fill the next cycle, browse our club projects collection.

BN
Bartholomew Ng

Bartholomew taught maths for years before switching to teaching Python. He writes about the basics of the language and about teaching code without drowning learners in syntax.

More posts by Bartholomew

More in Club Projects

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto