Creative coding as expression
Code as an artistic medium — canvas, shaders and generative systems as a way to make something, not just build it.
Most people see code as a tool: a means to build something that works. I also see it as a material — like paint, clay or stone. Something you don't just solve with, but express with. Right where code stops being merely useful is where it gets interesting to me.
Code as material
On a canvas, a screen becomes a surface to paint on. With shaders I don't paint with a brush but with mathematics — every pixel a tiny calculation, run thousands of times in parallel. Generative systems give me rules instead of results: I don't describe the image, I describe the conditions under which it appears. And then the computer surprises me.
That's the moment I never tire of. I write a loop, a little randomness, a curve — and something appears that I didn't plan and yet recognise as mine.
Building means reaching a goal. Making means letting yourself be surprised. Creative coding lives in the space between.
From solving to making
The difference is a stance. When building, I ask: does it meet the requirement? When making, I ask: what happens if I change this? The second question has no defined end — and that's exactly the invitation.
What makes creative coding special to me:
- Iteration is visible — every change to the code is instantly a different image.
- Randomness is a collaborator — used with control, it becomes a brushstroke.
- The rule is the artwork — not the single result, but the system behind it.
You don't have to be an artist to code this way. You only have to be willing to let an idea run without knowing exactly where it lands. Code then becomes a language in which you don't just solve problems, but say things that would otherwise have no form.