Today was the presentation of our final project and it went rather well. In the end we had to make some compromises on our final output that limited the range of detail that the haiku could capture, but all in all iKu575 functioned well enough to get our main concepts across.
Matt asked us what we learned from the making process that we wouldn’t have gotten from merely the design. At first I didn’t really know what to say. But now that we’ve had some time to reflect, I think there is one point that is crystal clear: any system or object that you design will impose some sort of structure or limitations onto the ideal form. These outside standards or infrastructures are always, in some way, shaping the final form or output of a device. In our case that was made crystal clear, both by our inability to fully grasp (in the relatively short time frame) coding possibilities, and the limitations of code itself. The interaction between language as we use it and coding language was a very difficult relationship to manage. As well things such as power sources and ethernet cables tied our device to a physical location. While in the design stage, these were elements that could be overlooked and imagined in the ideal form, but when the physcial making process begins, there are many choices and challenges that must be dealt with that ultimately affect the final product. This process of making has highlighted to relationship between the ideal creation and the realities one must deal with.