Programming Gloves and Debugging the Brooklyn Bridge

Lessons for academic researchers and developers learned by two ex-academics. Presented at SoundSoftware 2013 at Queen Mary, University of London.

Transcript

1. Programming Gloves and Debugging the Brooklyn Bridge Lessons Learned from Developing for Interactive Installations Becky Stewart becky@codasign.com becky@antialiaslabs.com Twitter: @theleadingzero
2. What we've been up to...
3. 2011 2012 2013
4. 2011 2012 2013
5. 2011 2012 2013
8. What have we learned from our post-academic work?
9. Get good at spotting the most common errors Practice at creating tests on someone else's code Challenge to think of solutions with a reduced set of resources Teach beginners
10. Document publicly Time up front saves time later Don't have to memorise the details Can come across own work on google searches
11. Expect last minute changes Code as if you know that you will be asked to change it at the last minute with little or no time to test Encourages modularised code Need confidence in code – needs to be tested! Have tests ready to run so you have some confidence that it will work out (and ways to quickly solve problems when it doesn't)
13. Manage expectations Help non-experts understand the strengths and weaknesses of the software Both for end users and tech transfer offices Boundaries of problem, algorithm, implementation
14. Useful frameworks Processing – processing.org OpenFrameworks – openframeworks.cc JUCE – juce.com
15. Becky Stewart becky@codasign.com becky@antialiaslabs.com Twitter: @theleadingzero