Showing posts with label ProblemSolving. Show all posts
Showing posts with label ProblemSolving. Show all posts

Mar 1, 2012

Why You Should Care about a "Scratch for HTML5"?

Why You Should Care about a "Scratch for HTML5"?

Should we teach programming? To everyone? Why?


I "teach" Scratch, though the focus is on ways of thinking, creativity, problem-solving, etc. I'm less focused on students understanding how their Wii or iPad games work, since Scratch is only going to give them a feel for that. The related question I always get from other teachers that is, I drive a car, how much do I need to know about how it works? Definitely some, or I might run out of gas or run my battery down, but how much more?

I just heard someone discussing something I thought might help me think about that question. I make toast, how much do I know about the toaster? Hmmm ... Here's the interesting answer:

The Afterword: Making a Toaster From Scratch

Thomas Thwaites: How I built a toaster -- from scratch (TED Talk)

Can't wait to read the book now.

Feb 13, 2011

John Seely Brown: Tinkering as a Mode of Knowledge Production

This video by John Seely Brown discusses many of the elements at the heart of BCS' Engage program.


  • Have to foster the imagination first
  • Create - Reflect - Share
    • sharing - create peer based learning
  • Studio Learning Environment
    • multi age learning community
    • best way to learn something is to teach it - Kids teach each other
    • critique - Need to be open to criticism (from self, peers, and others)
    • work in progress is public
    • critiques are public
  • Tinkering
    • with Information
    • with Knowledge
    • with concrete things
    • networked Tinkering with other people's stuff
    • you have to test what you build
      • authority comes from testing what you build and whether it works and is as good as it could be
    • Allows us to bootstrap our own knowledge
    • maybe - kids identities will come from what they have created AND others have built on
  • Technology
    • enables us to build distributed communities of practice
    • allow you to create and to remix

    Dec 1, 2009

    Anti-Patterns - Avoid Focusing on the Tool

    (This post the fifth in a series commenting on Kathy Sierra's presentation about creating passionate users.) 
    How many tool based workshops or training seminars have you attended? How much of what you learn do you retain? How much of what you learn is easily translatable into students learning about your subject matter and methods? Focusing on the tool instead of focusing on the thing the user wants to do with the tool is common among technology companies and professional developers. Over the past years we have tried to spend less time on the tools and more on pedagogy, content, and the balance among the three. We try to put the direct instruction bits into problem-solving activities, exploration and self-teaching, and a few examples of what students can do with the tools in their classroom.

    Yet, many teachers WANT, I mean demand, direct instruction in the step by step manner where they can write it down step by step. Are there ways to move teachers away from such a limiting habit? After all, how often does something occur in the exact same set of steps versus some variation on those steps? How will these teachers move on by themselves without the trainer their to hold their hand?

    What will it take for the majority of teachers to get to the point where many of their students already are, comfortable with exploring the tool, using trial and error or other methods of problem-solving, or if all else fails asking a peer or searching Google for a screencast or tutorial?

    As a half-way step. How can we get most teachers to at least see that their favored form of "learning" doesn't fit most of their students' favored forms of learning? This limits the possible growth of their students tremendously. Students' learning ends up happening far more outside of the classroom.