Reading Response #4
to Artful Design • Chapter 4: Programmability and Sound Design

Marise Van Zyl.
October 17, 2021
Music 256A / CS476a, Stanford University


Let me start by sharing something I happened upon while reading through Artful Design for the first time:

In french, the word for computer is ORDINATEUR, meaning
'one who puts things in the right order',..."

This quote from p.163 reminded me of another famous quote about music by Edgard Varèse on the definition of music:

"Music is organized sound""

Now considering these two quotes, surely this is the only justification for computer music we would ever need?
If music is organized sound, and a computer can organize sounds, then it is the perfect tool for music creation?

#showerthoughts

On to my reading response for this week....

Reading Response 4: Programming Experience *not* Required

Reading Artful Design (Chapter 4) this time around, I was less focused on the philosophical and more on the practical. I was focused on the code - and in this chapter, it really hit me. I struggle with coding. Perceptually, I understand code. I have a notion of how the computer thinks and how we tell it to do things. Practically, however, I just can't seem to grasp how to communicate with the computer. It's like we're talking about the same thing, but I speak English and it speaks Greek (or geek?).

Don't get me wrong, I am learning to code. Slowly but surely, I'm getting the hang of it. Yet, there feels as if there is something fundamentally missing with my way of thinking and doing that code heavily requires. Reading through this chapter, I understand what it says. I understand the goals, the ChucK examples, the principles, but still I feel like a toddler, trying to read Shakespeare.

Will I ever feel comfortable with code?
Will it ever not take me 4 hours to write one simple function?
Will I ever be able to do this?

Only (time) => will tell;