A couple of weeks ago, I was invited to join the Microsoft Technical Community Council (MTCC), which is described as “a group of external IT professionals influential in the IT Pro world, who are engaged and interested in sharing their opinions and meet once a month via a Lync call”. Basically, the Council is an opportunity for Microsoft to gain feedback from IT Pros with real-world experience of implementing Microsoft technologies and for those involved to understand a little more about the road ahead.
After some frantic NDA-signing, I was privileged to join the MTCC for a face-to-face meeting yesterday at Microsoft Research in Cambridge. Last time I visited Microsoft Research, they were on a different site, on the outskirts of the city, and some of the stuff I heard about, quite frankly, blew my mind. I was under NDA than (as an MVP) and under NDA again yesterday, so still can’t talk about what was discussed but the Microsoft Research website showcases some of the projects that have made it from the labs into the real world and describes the current areas of research.
We didn’t just learn about Microsoft’s Research operations though – there were other sessions – and the day also gave me a chance for me to meet with some of the people I’ve known for years but sort of lost touch with whilst my work was focused less on Microsoft and more on IT strategy – as well as to connect some faces to names – either from Twitter or, in once case, from my customers!
We also had rather a lot of fun, geeking out with Microsoft .NET Gadgeteer – a former Microsoft Research project described as:
“A rapid prototyping platform for small electronic gadgets and embedded hardware devices. It combines the advantages of object-oriented programming, solderless assembly of electronics using a kit of hardware modules, and quick physical enclosure fabrication using computer-aided design.”
Paul Foster (@PaulFo), whose antics I’ve written about before (on a home-made Surface table, among other things – and on PhotoSynth and Community Games) led us through an exercise more commonly carried out with school children, using Visual Studio with Visual C# Express and .NET Gadgeteer. Using modular kits we were soon building simple digital cameras, before going on to add LED indicators, current sensors, motion detection, etc. – with a drag and drop design surface and a few lines of C#. Even though I left it to the guys from Content and Code to crack out the code (I’ll do the infrastructure piece and plug things together!), I would confidently say that even I could have written the code that was required and it’s a very accessible way to get children doing something real with electronics.
Sadly, whilst the software is free, the hardware is a little on the pricey side, with an FEZ Spider starter kit coming in at around £200 (which is almost Lego Mindstorms EV3 money). Compared with an Arduino and some raw electronics components, that’s quite a lot more money but it should be said that the graphical design surface provided in the Visual Studio IDE is easier to use and the modular electronic components do make the Gadgeteer-compatible kit easier to work with. So, on balance, where the Arduino is great for “makers”, the Gadgeteer-compatible kit is probably a better solution for teaching kids the basics of controlling components with code.
Either way, it’s a lot of fun – and inspired me to start playing with electronics again… maybe I’ll even let my kids have a go…