So in the middle of reading Jim Groom’s post on The LMS is dead, and getting my head around next generational digital wonderment, I found myself jumping into Kin Lane’s post on the Personal API. As a programmer, I’m aware of what an API is and how it works, that it becomes a fundamental part of loosely coupled, highly cohesive system design, but I’d never thought of a personal API stack with me as it’s puppet master. Or it as my data shield…
On the one side, it’s good to give a nebulous thing a name – even better if you’re first to give it a name. It allows momentum to gather, and dialogue to take place. It allows hashtags and domain names and conference streams to beckon interest. On the other hand it allows labels to be generated and stuck to existing products. New improved recipe! Now containing organic Omega 3 hypermolecules! And when it comes to buying anything, it’s much easier to buy a neat and tidy defined thing with a simple price tag.
This post by Leigh Blackall is worth a read.
Lego is an interesting metaphor to choose for a next gen learning environment. Let’s build a spaceship! If only it were that easy. If only it was clear what construction was actually needed. In my experience of building platforms, it’s rarely clear. Competing voices, with competing features. But apologies, here I am talking platform once more.
According to the Educause report, the emerging needs of a NGDLE are these:
“Its principal functional domains are interoperability; personalization; analytics, advising, and learning assessment; collaboration; and accessibility and universal design. Since no single application can deliver in all those domains, we recommend a “Lego” approach to realizing the NGDLE, where NGDLE-conforming components are built that allow individuals and institutions the opportunity to construct learning environments tailored to their requirements and goals.”
I’m helping to run the code club at my kids primary school. Kids being kids, and adults being bombarded with ideas, it wasn’t too long before we had decided to build a “Don’t touch the wire” micro:bit based game for the school fayre. It works really well with the Micro:bit – it’s simple to code and deploy, and the simulator is knockout for testing and visualising a cheeky idea. Naturally, the winner will win a Micro:bit…