Creative coding in the age of AI

For a long time, creative coding was as much about patience as talent. Building a complex animation, setting up an unexpected interaction, composing an original visual rendering: all of this took time — a great deal of time — spent on technical problems often far removed from the original creative intent.

AI changes this equation. Not by replacing the creative developer, but by drastically reducing the distance between an idea and its execution.

The value of an AI assistant in a creative workflow is not in automatically generating perfect code. It lies in removing friction. The time spent hunting for the right syntax, debugging a configuration, writing repetitive utility code: all of that can be delegated.

That recovered time becomes time to think. To test visual directions. To revisit an animation and push it further. To question the intention behind an effect rather than the lines of code that produce it.

What AI does not do is decide. It cannot tell whether an animation should feel soft or sharp, whether a scroll should resist or glide, whether a colour should breathe or strike. Those choices belong to the developer who understands both the code and the sensation.

The designer-developer profile — often seen as an in-between — becomes particularly relevant in this context. The ability to think visually and to implement precisely is a combination that AI amplifies rather than threatens.

One of the most tangible effects: you test more. When exploring an idea takes thirty minutes instead of three hours, you try more directions. You abandon what does not work more readily. You iterate.

That may be the real shift. AI does not generate creative ideas. It makes their exploration less costly. And for a creative developer, that is a new kind of freedom.