I found the interview hard to follow, so I'll just focus on a few bits. I disagree with the idea that mathematics has limited computer science. I think the aut

I found the interview hard to follow, so I'll just focus on a few bits. I disagree with the idea that mathematics has limited computer science. I think the author has a belief that mathematics is a one-way street: you can use mathematics but you can't create it. This is not the case. He's correct the standard mathematics (say, undergraduate level engineering mathematics) doesn't model changes over time and other things that are interesting about computer systems, but this doesn't mean that new mathematics that does model these things cannot be created (and they have). It's also important to realise the practical limits of maths. Unless you're a pure mathematician you don't create maths for the hell of it---you create it to answer some question (what is the runtime of this code? Is it memory-safe?) Modelling everything is hard so you only model enough to answer the question of interest. I agree that there is an artistic aspect to programming, and I can think of two interesting applications to this. Firstly is to study programming as an art, and this is something the relatively new Programming journal and conference (see https://programming-journal.org/ https://programming-journal.org/) is trying to do. I think it's early days yet and we don't really have good vocabulary or processes for this study. The second is to use teaching techniques from art, such as studio learning, for programming. I think this could be really valuable and is very under-explored.