Course Feedback

I enjoyed the concept of giving us weekly assignments to keep us occupied as well as learning. There is no better method of learning than by actually doing. Additionally, people in the class all came in with varying levels of knowledge, and for them to have to learn everything about electronics is unnecessary. With doing things by hand, the level of complexity is determined by one’s self.

I enjoyed the classes where jet would bring in and show us various links online of interesting projects. Firstly, it was good inspiration for our projects, and secondly for someone not coming from a purely artistic background, my exposure to this “culture” is very limited. It was very interesting to see what people are doing in this design space.

The idea of having a fairly complex midterm project forced us to push ourselves and understand how long building something would take. I learned from my midterm fiasco and began planning my final project much earlier.

The class blog is also a great place to look for ideas, assistance and just a simple, easy to use information interface for everyone. I’ve never used a blog for a class, but I think it is a great tool.

There was hardly anything I felt negatively about in the class. My comment is more of a suggestion to improve the class for others. I felt that diving straight into Arduino code was difficult for many people who did not have a programming background. I would suggest, the first few classes should be devoted to getting the class to think in steps, block diagrams, flowcharts etc. this way it is a little less daunting than having to decipher a foreign language.

Reflecting on the semester that was, I have really enjoyed this class for two major reasons. The freedom it gave me in pursuing projects that brought enjoyment to me and really giving me confidence in my ability to learn and undertake tasks associated with electronics and microcontrollers.

Final Writing Assignment: Class Critique

In attempting to come up with ways to improve the class, I have yet to decide if it should be changed or left the way it is. Foremost in my mind is the loose structure. We are taught some basic coding skills and given some fundamental assignments and then left to our own devices. While some would say this lack of structure provides no basis for learning, I believe this unique environment has allowed for maximum exploration and project development. Of course, this means the students must be motivated.

I disagree with anyone who says there should be a programming prerequisite to this course. The resources are available, be it the professors, other students or the internet. I found that between those three resources, I was able to solve the problems I encountered and learn new skills.

Still, there are a few things I would add. I would require students to find more outside projects to share with the class. This is not to say that I feel the projects we did were limited by any means, but an extra push to get us to find out more about the interactive world could only be a benefit.

I wish there had been other scheduled help time during the week. Near the end of the semester Mark invited us to come to the Code Lab a few times, but I would have liked more regular after-hours help sessions.

One of the most successful things in the course was the appearance of guest lecturers. I thoroughly enjoyed them, especially knowing they were right here at CMU. I hope they present again for subsequent classes.

As an addition to the course, it might be interesting to replace the mid-semester project with a group project, or create a second class for doing group projects. It might also be more feasible that way to use some of the technology available at CMU, such as laser cutters and 3d printers. I also believe the projects created could be even more interesting and amazing than the ones we saw this semester.

Overall the course was a very successful one. While, at its core, it should not be changed, a few additions could easily make it one of the most desirable and popular architecture electives.

What is worth interacting with?

Given the opportunity to apply the technology and techniques we learned to anything, for some reason I chose to work in the same problem space I have been in my design classes. With projects like the pushpin and especially the electronic book reader, I have already been applying what we’ve learned to what I currently imagine I’ll be doing for a living.

What I think I need is for my work with sensor technology to not apply to industrial design. In the future, I’d like to apply what I’ve learned to more pointless creations. There is a great opportunity to explore and play with the technology. Having more open-ended goals for what the ‘thing’ might be could result in learning a lot more about the possibilities that a little circuit board, some programming, and a few electrical devices can bring. I’ve made a few finished* products, but what I think I need is less making and more hacking, less finishing and more playing. It’s something I find hard to do at school, and I feel like this class didn’t do enough to promote the process either. Nevertheless, by exploring both extremes of creative problem solving, the conceptual and the technical, I hope there is a lot more meaning that can be brought to the middle, where design can change the world.

Next semester I will be taking a furniture design class where I hope to explore how technology can enhance or change the meaning of objects we sit on, work upon, sleep on, etc.

Having reached the level of accomplishment we have now gotten to, I think more discussion on the merits and demerits of technology-based interaction should be continued. Right now, interactive/smart products and buildings seem to be very attractive. Objects that can adapt to people will last longer and gain more importance in our lives. But still, I wonder how future saturation of these objects might change our perceptions of interaction. Given our biological and cognitive limitations, and the limited resources we have on this planet, what will be worth interacting with?

*hardly