During the project, I did experiments to imagine different ways we can think about what code is; how it looks like and how we relate to it. In this short video, I explain how programming is boxed into a tool for efficiency; which if we see programming as an art is limiting.
Let’s compare programming to painting. In painting there are two types of painting; whiting a wall or creating a piece of art. In programming it seems like we didn’t find the paintbrush yet; we have been making better grips (for f.e. smaller hands) for the paint-roller but didn’t change the expressive part of the tool.
I will guide you through my experience of using other existing tools and re-formatting them to create explain and explore a different idea. In this case, more visual-based tools are used to define the behaviour of more physical based interactions in the real world.
These experiments are described on the website project hub; which was a double-edged sword; it helped me understand how sharing in the community works and it helped me explaining my concept for a broader audience. This is more aimed at the design community which is usually quite familiar with graphic design tools (Adobe Suite) and bridge this to the physical computing field. What these experiments try to do is to expand the concept of ‘code‘ and programming beyond the written text.
There are two benefits to using already existing tools; people are already familiar with them, if they are well known in the community and it is an easy (low-cost) way to imagine different ways of defining behaviour, then having to design a new whole ecosystem.