It infuriates me that stuff from the Internet routinely doesn't include all the credits. Because as soon as I listen to something, if I like it, I want to know, "Who's the bass player?" "Who did that?" "Who's the engineer on this?

I'm bloody awful at multi-tasking.

I'd rather hold one note for an hour and modulate it so that it means something than play 3,000 notes in 15 seconds.

Except in a few cases like Music for Airports, which was a very clear case of noticing a niche [and] saying, "Okay, there's this situation in which people always play music, and nobody has written music for that situation so I'm going to." So, that was a very clear example of spotting a niche and working for it. I have done that occasionally.

A lot of the so-called systems composers have this thing that the system is always right. You don't fiddle with it at all. Well, I don't think that. I think the system is as right as you judge it to be. If for some reason you don't like a bit of it you must trust your intuition on that. I don't take a doctrinaire approach to systems.

When you build a building, you finish a building. You don't finish a garden; you start it, and then it carries on with its life. So my analogy was really to say that we composers or some of us should think of ourselves as people who start processes rather than finish them. And there might be surprises.

I think very often producers are really trying to repeat things. When they hear something in the new songs that they recognize as being a bit like something that was a success on a previous record, they're inclined to encourage that.