Programming Gloves and
Debugging the Brooklyn Bridge
Lessons Learned from Developing for
Interactive Installations
Becky Stewart
[email protected][email protected]
Twitter: @theleadingzero
Slide 2
Slide 2 text
What we've been up to...
Slide 3
Slide 3 text
2011 2012 2013
Slide 4
Slide 4 text
2011 2012 2013
Slide 5
Slide 5 text
2011 2012 2013
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
What have we learned from our
post-academic work?
Slide 9
Slide 9 text
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
Slide 10
Slide 10 text
Document publicly
Time up front saves time later
Don't have to memorise the details
Can come across own work on google
searches
Slide 11
Slide 11 text
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)
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
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