I took some time the other day to go to the Tate Britain and catch the Hepworth display. I had mixed feelings about it tbh – it was rather short and the curation was a bit odd. I didn’t get a sense of time and influence from the layout of the work so it was hard to get the context of each piece. That said, there were some remarkable pieces in there and it’s worth a visit.
I got home and felt like writing some code and so built this response to what I’d seen. I’ve always been struck by Hepworth’s use of string and the similarity with the mathematical models which I used to be fascinated by at the Science Museum when I was a kid. There is, of course, a direct influence which the exhibition touches upon here and there. In this, we see the influence of science on the arts at this time, and a direct reference in her work to non-artistic methods of visualisation.
It’s a bit of a work in progress this, limited to straight lines rather than the arced forms which Hepworth so beautifully renders. Maths is hardly my strong point but I’d like to crack that next.
What did strike me, though, was how like an artist’s process the workflow of writing code can be. You’re building something through process, shaping function and form from the clay of the tooling (language and frameworks). Making aesthetic decisions, sure, but also following a craft to create your vision. I’ve touched on this before in my experience of playing music, but I think it must be even more so with sculpture.
I suspect that all programmers could learn a lot, not only from the practises of artists, but also from their routines and the development of their craft. When I was in Barcelona earlier this year, and spent a hugely emotional afternoon at the Miró museum, I immediately bonded with the idea of Miró’s trips out of Spain to Paris in particular, where he connected with other artists. This is also true of Hepworth, whose associations, particularly with Nicholson (obviously) and Mondrian can be traced through her early work. In that respect, coding communities do a great job in bringing movements in coding together.
One could argue that we’re in a golden age of community-driven quasi-artistic movement in code. In the spirit of innovation, I’d strongly recommend learning a little about how artistic movements have helped shaped the work of great artists, and drawing some inspiration from the organic developments in the history of art which resulted.