That’s the phrase that summed up day one (UPDATE: & Day 2) for Craig Wallace on the stand and he is not prone to exaggeration 😉 We were supporting and listening in thanks to the magical powers of social media and live stream and it really was a day crammed with teachers soaking up the CPD opportunities of which there were many.
We’ve done our best to Storify our tweets and those of teachers with whom we connected. This was an incredible event for us and we’re so grateful for everyone who came to see us to learn more about Blippit’s App Maker and other computing tools.
We were asked by so many people who they might get involved that it we’re now actively seeking out people who might suit becoming learning champions – Blippit Ambassadors. If that’s something you’d like to know more about just email firstname.lastname@example.org
If you’re feeling really brave scroll right to the bottom of this post to see what happens virtually at Blippit Australia HQ. This is not the kind of Python we like.
All software applications have bugs – some cause no real problems and go unnoticed, others are minor and a minority wreak havoc. You might be surprised to hear that software providers LOVE hearing about possible bugs via bug reports. They love it even more if the steps that lead up to the strange behaviour can be replicated by their Application Development Team because this means the bug is real and can be fixed.
Without the help of users (essentially many hands and eyes) application developers can’t hope to capture every bug for debugging try as they might.
In the classroom it’s a fantastic exercise to give students a simple program with a bug or two it. This way they really REALLY have to
be systematic in their approach – record steps taken etc
be tightly focused on isolating the area where the bug is likely to be
be able to step through the programme in it’s component parts or sections
develop an understanding of how the larger whole can be viewed in chunks
Here at Blippit we were able to find and de-bug a FANTASTIC bug in quick fashion this month thanks to two schools who took the time to file a bug report (they told us about it basically) to email@example.com . This lead to more detailed info gathering, a school visit from us and finally within a week and a half a global update of Blippit IO. They helped us improve Blippit IO in a measurable way for the thousands of students and teachers who are using Blippit IO across the UK, Australia and US.
If you’re a lovely Blippit IO User, we are going to make it nice and easy for you to report anything that feels like a bug to you soon. More about that to follow.
So…the moral of this story is, if it’s safe and legal to do so, always tell the people who wrote the code if you find what you think might be a bug in their app. They’ll never be offended, they’ll always be grateful and the rest of the community using that app will put you on their cool list.