CoderDojo Kids STEAM

CoderDojo “Interactive Web” Session 1

April 23, 2014


CoderDojo “Interactive Web” Session 1

Yesterday was the first session of a new series I am teaching. Organized by CoderDojo, the session was geared towards kids who have prior HTML experience. Through the series, I am going to introduce kids to interactive web development and Cloud services. We had the session at Microsoft’s Silicon Valley Campus and had a full-house. My daughter Gia was a co-presenter.

In this session, I introduced the kids to CSS and added a fun design element. They had to create their own Mondrian art, using CSS.

Here are some stats on attendance:

Ages – how many attending

  • 9 years old – 12
  • 10 years old  – 8
  • 11 years old – 14
  • 12 years old -12
  • 13 years old – 8
  • 14 years old – 4

29 boys 27 girls

Experience with HTML

Hours – how many attending

  • 1-10 hours  – 23 ( but should have had previous web class)
  • 11-20 hours  – 20
  • 21-50  hours-  9
  • 51-100 hours – 2
  • 100+  hours- 2

And some session materials:

Session Handout (PDF)
Session Deck (PDF)

And finally, some photos:

IMG_6520 IMG_6521

Here’s a tweet from nestGSV’s Julia Figuerido who made her mentoring debut at CoderDojo:

Founder NftyDreams; founder Decentology; co-founder DNN Software; educator; Open Source proponent; Microsoft MVP; tech geek; creative thinker; husband; dad. Personal blog: Twitter: @techbubble
  1. Lucazeau Daniel

    Hello, files are no more downloadable. Do they contain some specifications on the attempted result? Best regards D. Lucazeau

  2. RadioSky

    Seattle had a project celald 6 hour startup that met a couple of times a year to code a project on a saturday. to my knowledge it hasn't been around for a while. their objective was to either build a usable product, or expand on past project.I think this could work if the objective is clear enough, and there are enough people so that it can be handed off. What if twice a year, we selected a non profit and built a solution for them. each week would be a sprint. we'd do major work together on the weekend, and do minor bug fixes in spare time during the week. when the sprint is over, you can opt out the following week and let someone else do it. so you only own the code during the current sprint.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.