What struck me when I got the Arduino board was, how small it is, how small all of the things are. And that means, that they will be far less obtrusive than I had previously thought. And seeing how easy it is to work with I look forward to learning a great deal.
The next step is to get to grips with the coding. Fortunately there is a lot of help on the web and even if some piece of code is not exactly what I need, I feel much more confident to be able to tailor it to my needs.
How do I feel about using digital sound in conjunction with sculptures? I have always felt there is an equivocal relationship between sculpture, or statuary to be more precise, and sound. Is a statue not meant to be silent, to be contemplated without the distraction of noise?
But what if the sound comes from within, trapped, allowed a small breathing hole to reach one’s ears, fingertips, barely audible, sensed; a sound that is neither music nor the result of some kinetic accident? I see the sculpture as the receptacle of its own soul, the embodiment of what it is in its nature to be gently radiating outwards, translated into vibrations seeking connection.
There is of course an element of humour in all this, for it to be otherwise would be melodramatic and to what end: humour can be poignant, questioning, engaging, cathartic. All I know is, I go with where the work takes me as it also follows me.
Six months ago I started with a loose pool of ideas flowing from existential themes. My main aim since then has been to find a cogent argument that reflects my various interests and that could place in different arenas. This quest has been exciting if onerous; I have gone down many wandering pathways. However, I also have had to discipline my thoughts within a varied practice since many of my ideas emerge synchronously with my practice and two years is not that long to develop a coherent trajectory. I know that the Research Statement will need to be started soon and that it needs to be well conceived at the outset in order to avoid time consuming blind allies during the Summer months, a period good for making.
In view of the upcoming RS, I have looked at the problem both taxonomically and mereologically, reductively and holistically. The tension between these two ways of organising thoughts has helped me identify those ideas and practices that would fit a tight set of self imposed requirements:
- flexible and focused
- leading to a project proposal and higher research
A thesis emerged ten days ago in conversation with Janet, not by logical deduction but in moment of gestalt in which I saw a bigger picture. With few words I was able to state the obvious precipitated out of the wanderings and writings I have done over the past six months. But how could I be sure this would hold together? I wrote a preliminary abstract or outline of the thesis in a surprisingly short amount of time, much shorter than the time it has taken me to get this far on this post. Since then I have been able to add content and ideas without disturbing cogency. I was concerned about having to read scores of papers and dozens of books in search of an idea. Instead, I know where to go and what to read for corroborative material and help to shape the argument.
I shall write about the RS in future post but for now I wish to continue with what I am doing. Instead I have opened a folder for placing material separate to the blog. Today (yesterday) I went to Doncaster to buy materials, time flies.
Briefly the RS tries to bring together in artistic thought:
- The Cambrian Explosion
- Early Bronze Age civilisations in the Fertile Crescent
- Medieval thinking
- Science fiction
- The digital environment
- Coding of information
- Algorithmic development and chaotic order
Yesterday we were introduced to the intricacies of coding in java, by Paul Abbott, with a little html and css thrown in just for fun. It was difficult to follow at times, particularly juggling four different windows at one time, thank heavens for a large screen. It felt like having to catch four piglets and trying to put them into a shallow basket… with boxing gloves. However, I survived and took away some valuable ideas that will help me, particularly when I look at the video recording of the session again. These notions can be summarised in a very cursory way as:
- Types of coded information are kept in discrete blocks.
- One block of information tells another what to do and the different functions and variables in each one has to correspond to those in another block.
- The process is like constructing a flow chart in your head. For that matter, drawing a flow chart when planning code is not such a bad idea.
- Brackets hold different types of information.
- The syntax of the code has to be precise.
- Practice by copying and pasting existing code and alter one parameter at a time and see what happens. Make sure all corresponding parts match one another.
- It is no good just reading about code, you have to do it as you go along to understand anything at all.
I do not know how relevant coding is to my practice. It is immensely satisfying, though, when a piece of code works. I know from my scant experience with html and css. However, it is a totally different language and I struggle enough with words. So, although I may tinker with some code and perhaps even build a rudimentary something for the internet, I think I shall leave this one to those better suited for this activity. One thing, as Paul mentioned, it does help when you can converse in the same language with someone if you need something doing or collaborating on a given project.