Skip to Content
Skip to content
Polyphony Solutions
All articles

Creativity in Technicality: Pictures, Sound, words and scripting.

On mathematics, music and learning to approach a problem from more than one direction.

11 November 2026 by
Creativity in Technicality: Pictures, Sound, words and scripting.
Polyphony Solutions Ltd, Luke Austin

My grandad taught me to programme pictures. My dad taught me to paint with sound.

I grew up with my grandad, who introduced me to computers and mathematics and had me programming Mandelbrot set visualisations at the weekends. Together, we would keep zooming in, looking for miniature versions of the familiar shape hidden within the larger pattern. It was incredible to me. You can try it yourself in this Mandelbrot explorer.

His outlook was overwhelmingly logical and utilitarian. He liked things to make sense and generally preferred them to have a discernible purpose. Here, the purpose was to teach me about fractals and the mathematics behind them. I was also discovering how much there could be to explore inside a picture generated by a mathematical rule.

My dad was a musician. Through him, I learned another way of making something: working with sound, giving it shape, listening to how the parts affected one another. Painting with a different set of materials.

My grandad’s father had been a painter, and the two of them were always at odds. My own artistic interests, whether drawing, painting, writing or music, were never things my grandad took seriously.

I’ve often felt like a synthesis of those creative and technical influences, which could occasionally frustrate him. There is a gentle irony in him teaching me to programme pictures: he was giving me another way to bring together the very things he tended to keep apart.

I don’t think either of us would have described it that way at the time.

A picture made of instructions

A Mandelbrot visualisation gives you something extraordinary to look at, produced through a precise mathematical process. The image has structure because the calculation has structure. You can change how you explore or represent it, but you cannot persuade the underlying mathematics to behave differently because you would prefer a more attractive result.

That combination still interests me: something exact becoming the basis for something you experience visually.

Programming lets you move between different kinds of thought. You need to understand the instructions well enough to make them work. Then you look at what they produce and decide what to try next. The result becomes part of the enquiry.

I would be giving my younger self rather too much credit if I claimed to have understood all the implications. I can recognise something familiar in it now, though. I still enjoy the movement between understanding a mechanism and exploring what I can do with it.

Painting, music, mathematics and computers offered different ways of making and understanding things. I have never been particularly good at keeping them in their respective boxes.

A difficult influence

My relationship with my grandad was hard. He was a difficult man.

His influence on me included the things he deliberately taught me and the things I learned through the difficulty of being close to him. It would be a selective account to describe the computers and mathematics while leaving that out.

He worked for Marconi on weapons systems, something we perpetually disagreed about. Our differences went beyond whether we found the same things interesting. They included questions about purpose: what technical ability should be used for, and whether making something work was sufficient justification for making it.

I can value what he gave me while continuing to disagree with him. I can recognise his formative contribution without pretending the relationship was easy.

That experience also taught me something about handling difficult situations. I think part of it was learning to stay with a disagreement long enough to understand it, without assuming that understanding required agreement.

It is a lesson I still have to apply deliberately. A strong personality can make a conversation feel as though the immediate task is to win, concede or find a way out. Finding the actual question underneath that pressure takes more care.

What is being argued? What matters to each person? Where is there something useful to work with, and where does a boundary need to remain?

I wouldn’t turn a hard relationship into a convenient training exercise. But it is part of how I learned to deal with complexity between people, alongside the complexity of the things they build.

Years later, I was programming the weather

One example of those creative and technical influences coming together was an animated advert I made for The Oversight.

It had a snowy scene. I worked with an existing snow component, and my contribution included programming the wind: changes in strength and direction as the advert moved through its sequence. Ironically, my Grandad started out as a meteorologist. He would have laughed at the inaccuracy of my depiction.

When we recovered the old files, I initially remembered having written the whole snow algorithm. Looking at the work again prompted a more modest recollection. Perhaps it had been the wind.

Apparently, memory is quite capable of awarding itself a larger development credit.

The distinction matters. The underlying component was somebody else’s work. My contribution was in how I used and extended it within the advert.

The technical task involved controlling behaviour. The creative task involved deciding what that behaviour should contribute. The snow had to work, but working snow was only one part of the composition. Its movement sat alongside the words, their arrival and departure, and the timing of the whole piece.

There was no single calculation that could tell me whether the wind served the advert. I had to watch it.

I could express a change precisely in code, then judge its effect as part of something visual. That feels like a descendant of programming those mathematical pictures: understand enough of the mechanism to make deliberate changes, then pay attention to what the changes produce.

Painting with sound

“Painting with sound” is how I think about what my dad taught me.

It gives me a way to describe music that includes both its construction and its effect. There are notes, instruments, timings and technical choices. There is also the experience they create together: where the attention goes, how a passage develops, what changes when something enters or falls silent.

In production, I can record changes in volume, EQ or effects and play them back consistently. That gives me repeatable control over decisions I have made. I still have to listen. The fact that a movement can be programmed precisely tells me very little about whether I have chosen a good movement.

Sometimes the useful decision is to leave room for somebody else.

When I recorded the performance behind Sea Change, I had no idea what my brother was going to play. I simply pressed record and gave him the space.

He brought something I couldn’t have specified.

That is an important experience to carry into technical work. There are situations in which I need to define the result closely. There are others in which somebody’s contribution is valuable precisely because it exceeds what I would have thought to request.

Making room for that contribution involves judgement too. I need to recognise where precision helps, where it becomes restrictive and what I need to understand before deciding.

A recording can be technically prepared while the performance remains open. That is a combination I find useful well beyond music. I can know that something is possible and have a workable path towards it, while still approaching it differently each time. Understanding how to make it work gives me room to explore, and a basis for judging whether a different approach serves the result.

Finding a structure that serves the work

Business systems put these ways of thinking into contact with practical obligations.

A customer has been promised something. An invoice needs to be correct. Stock needs to correspond to what is actually available. People need to understand what they can decide and what happens next.

There is plenty here that benefits from precision.

But the work begins with an organisation that already has its own history, relationships, habits and expertise. Some of its apparent untidiness may be protecting something valuable. Some may simply be the residue of a problem solved in a hurry several years ago. Understanding the difference takes more than knowing the software.

I enjoy that stage: seeing the current state, with its accumulated workarounds, and beginning to understand how the pieces might be brought into a coherent structure.

The creative part is in recognising possibilities and deciding which relationships matter. Technical understanding gives those decisions a dependable form. Each changes the other. A promising idea may fail when examined closely. A constraint may prompt a better idea than the one I started with.

The conversations matter just as much. People can disagree about a proposed change because they understand different parts of the operation, carry different consequences or have experienced previous attempts that went badly. The force with which somebody makes a point does not, by itself, tell me whether the point is sound.

I need to understand what they are protecting and examine the reasoning. That leaves room to learn from an objection, challenge it or hold a boundary without making the whole discussion a contest between personalities.

This is also where I have to resist my own enjoyment of solving the puzzle. A satisfying arrangement is not sufficient justification for changing somebody’s working day. It needs to help the people doing the work, preserve what matters and make the business more understandable.

An unusual solution has to justify the effort of building it and the responsibility of maintaining it. A familiar solution deserves the same scrutiny.

Creative judgement needs contact with consequences.

Keeping the influences together

I don’t think of creativity as something I add after the technical work is finished. It influences the questions I ask, the connections I notice and the possibilities I consider.

Technical understanding gives me a way to examine those possibilities, discover their limits and make some of them dependable.

That combination has taken different forms in my work: a mathematical image, programmed wind, a recording, a business process. The materials change. I recognise a similar curiosity in each.

I cannot trace every choice I make back to an early influence, and I would distrust an account that tried. People are more complicated than a tidy origin story.

But I can recognise what I was given, and acknowledge that some of it came through a difficult relationship. Gratitude does not require me to edit that difficulty out.

My grandad taught me to programme pictures. My dad taught me to paint with sound.

I still enjoy finding out what becomes possible when those ways of thinking meet.

In my work, that means being able to move between the overall shape of an operation and the detail of how somebody actually gets something done. A structure can look elegant from a distance and become bewildering for the person working inside it.

Perhaps that is another thing those afternoons with my grandad left me with. I still want to zoom in and see whether it makes sense.

What needs to work better in your business?

Facing a consequential decision, an operational problem or a change that needs leadership? Start with what the business needs to achieve.