A reflection on going beyond coding when thinking solutions and the Digital Technologies curriculum.
I attended an eLearning session recently where the participants were asked to place ourselves along a continuum in regards to their confidence in regards to the Digital Technologies curriculum. At the far end of the continuum was the idea of ‘coding your own reporting program’. The conversation the ensued was intriguing. “That is not me … I could never do that … You need to know a lot of Excel for that.” To me this only tells part of the story associated with digital technologies.
When you look at something like a reporting solution, we need to start by addressing the problem being addressed? This is why there is a focus on design thinking in the curriculum. A part of this process can be identifying what other solutions already exist. If there is already an application that addresses the problem you are trying to solve, why would you start again?
Alternatively, it is important to work out if there is something you can start with and build upon. Maybe a solution that you have found only addresses a part of your problem, but offers a starting point. This may include some pre-existing code that can be adapted. That is the power of a open platforms like GitHub and Scratch, where you can not only access other people’s code, but share your own iterations.
Another twist is where you might develop a first iteration and then bring others on-board. At some point a solution may benefit from incorporating other skill-sets, perspectives and resources. For example, at some point Gmail went from being somebody’s 20% project to something being developed by a team. In an interview with EdTechCrew, Adam Bellow reflected on the development of eduClipper. After some initial work, he outsourced the creation of a new platform to an outside provider. He then took this iteration and refined it further. This is not to say Bellow could not code it himself, but when we get to systems thinking, there is sometimes more efficient and effective ways of working.
So when we ask the question, can you create a reporting solution, maybe we should ask why are we doing it and has someone else already laid the groundwork? This is something that comes through in Doug Belshaw’s work around digital literacies, such an activity is bigger than whether or not you can code.
So what about you? What has been your experience of coding? Comments welcome.
If you enjoy what you read here, feel free to sign up for my monthly newsletter to catch up on all things learning, edtech and storytelling.