Today’s post is by guest author Bea Leiderman. Bea is a technology coach at Goochland County Public Schools in Goochland, Virginia, where she helps middle and high school teachers use technology to design effective learning opportunities and environments. Bea has won numerous accolades for her innovative teaching, and her work with colleagues incorporating Agile / SCRUM to transform learning projects was featured in the June 2016 issue of ISTE’s entrsekt magazine. Bea is the author of six books of insect macrophotography and a book about iBooks Author, all available on Apple’s iBooks Store. You can find more of her amazing insect photos on Flickr, and can follow her on Twitter, where she also has a channel for insect photography and information.

A complex Final Cut project
For as long as humans have been alive, we have been problem-solvers. The idea of designing solutions and executing them did not come about with the advent of the personal computer, although the personal computer and other related technologies do make the iteration of approaches and ideas so very convenient. This might be why Steve Jobs said in a 1990 interview that a computer is “the equivalent of a bicycle for our minds,” allowing our creative and problem-solving processes to go so much faster.
Coding in particular seems the most obvious method for teaching the design-and-iteration process that develops creative and critical thinking skills. Using coding is transparent, and it is easy to contrive ways of bringing coding into the traditional school schedule. It is also easy to dampen the joy that comes with ideating, designing, and executing an idea when coding is adopted as the only way to do so. As much as we might think we are helping students be creative, by making them all learn “coding,” whether they are interested or not, reduces coding to the same level as anything else we have ever forced upon children in schools.
I’m not against the idea of teaching coding, but I believe we are pushing too hard in the wrong direction. We don’t all need to know how to develop apps, as fun as it might seem to some, especially because each of us have our own particular idea of fun and our own plans for our future. Knowing how to code is not as important as knowing the ideas behind coding: designing a process and making it happen. If indeed all jobs will require coding in the coming century, everyone will have a better incentive than a grade on a report card (or *gasp* a standardized test) to pick up the skills. Continue reading →
You must be logged in to post a comment.