I spent most of my spare time this week working on this site - and publishing it! Also wrote more project pages, like Sun of Denmark and Wall Art.
I should have received components for Project Caramel, but since that didn’t happen there will not be any progress on that project this week.
Project Cocoa
Instead, I started Project Cocoa. I thought the name would be appropriate since the idea is to design a heater cover for friends of mine that renovated their apartment recently. The intention is to design it in laser cut MDF and paint it afterwards, and a fun way of playing with parametric ideas. I got measurements from them, and started drawing up some pencil sketches, and then moved into Grasshopper to try some out.
Building up a sketching workflow in Grasshopper
Including people for sense of scale
Rough placement in context
Next step is to flesh out more sketches. I’m curious about exploring other, less purely geometric principles like magnet fields or physics.
Frequency and refinement
I think about frequency a lot. In preparation for Project Caramel, I read The Scientist and Engineer’s Guide to DSP. Specifically, about Fast Fourier Transforms and how you can use it to go from looking at a signal in time-space to frequency-space.
In the context of interaction design, I think about the frequency of prototype iterations and product releases. During my first five years at LEGO, I have launched two products. In my experience, 2-3 years for product development isn’t unreasonable when developing something that’s both physical and digital. Say I have 30 years of career left, that’s 10-15 products I have left, a frequency around 9 nHz, or 0.28 cycles per year.
One of my hobbies is coffee brewing, and most of the baristas I have met say they serve hundreds of cups of coffee in a single day. As frequency of iterations, that’s 3,170,979 nHz, or 100,000 cycles per year. Not sure what this means or how to think about it, but it’s on my mind.
Site
I have extended the structure so that beyond this blog, but also project pages that I can create for each project. Did lots of styling, built first mobile support, and streamlined the look on the different parts of the site.
First week with this new site. I’ve spent a couple of evenings setting up the site, my github repo, and modifying the site theme and writing these articles.
Project Caramel
The first side project I want to start writing about is Project Caramel. Why Caramel? Working on confidential projects in my dayjob, I’m used to working with codenames. Besides being a fun way to reference what you’re working on, I think it gives freedom to allow the thing you’re working on to develop independently of it’s name. In blogging, I’ve seen it used by Tom Armitage, who I think uses it because of client confidentiality. For these personal non-confidential side projects, it’s about having a way of referencing a project while the idea is still developing.
Concept
Project Caramel is an old idea I had while studying. I was curious about creating more sensuous interfaces that allow for expressivity and mastery. Think about how a piano or keyboard key has the notion of velocity and even aftertouch, while a keyboard key is binary. What if the keyboard keys were sensitive to the way you strike the key? Like typing harder would switch to caps?
I want to explore ideas of having interfaces be a natural part of a surface rather than something that’s mounted onto it. Like if the wood itself was the interface rather than a button coming out through it.
Components
First iteration of the prototype I’m building to explore the concept consists of:
My thinking is, by picking up the audio signal from a surface as I interact with it and performing signal processing, I should be able to quantify interactions.
There’s a lot going on here. Electronics, designing and developing the circuitry needed to properly pick up the audio signal. Firmware development, developing the DSP algorithms needed to qualify the signal. When electronics and firmware is up and running, I will move into the industrial design, designing and prototyping the surfaces that explore the design space that I suspect the sensor opens.
What’s the end-game? the output? I belong to the school of Researching Through Design / Thinking Through Making, where the meaning is something that emerges as you actually start developing and embodying the idea. The answer for now is, I don’t know.
This week
For this week, I researched amplifier-, limiter-, and filter-circuitry, and attended a HackChat Event on signal conditioning with Jonathan Foote. It informal yet informative. The format invited a lot of sharing from everyone present, and after the event I had purchased two new books and had 10+ new tabs open with subjects to research.
I also purchased components for prototyping the above circuitry, which should arrive next week.
Hi, welcome, you made it. And since that’s the case, so did I! I’m Kevin, and I work as an Interaction Designer at LEGO.
This isn’t my portfolio. This is where I display and blog about my side projects. Since leaving the Scratch Team and the Media Lab last summer to go back to Denmark, I miss being part of a community that’s interested in the intersection between art, design, and technology. And living in COVID-19 lockdown for months, I am feeling even more alienated but also exhausted. Since my day job is mainly working on confidential future products, I can only share it with a small circle of people. Working remotely, that circle is even smaller.
This site is an attempt to increase the size of my circle by making it revolve around a thing - either physical, digital or both.
Blogging
Since my side projects, like my day job, are often a mix of physical and digital components, and often require me to learn a new skill, they take longer to develop.
The primary inspiration for making this site was Matt Biddulph who I met at a conference last year. He runs the hackdiary, but also launched an instagram profile for his side projects. It got me thinking, that a space dedicated to side projects might be what I need.
Inspired by Tom Armitage, I’m planning to use codenames for some projects. Partly, to be able to talk about them while keeping them private until they’re ready to show, but also perhaps to talk about them before I understand what they are.
