The Creative Technologist Manifesto

I call myself a creative technologist because the existing labels do not fit. Engineer suggests someone who implements specifications written by others. Designer suggests someone who works in Figma and hands off mockups. Artist suggests someone unconcerned with functionality. None of these capture what I do or what I aspire to do.

A creative technologist works in the space where these disciplines overlap. The code is the medium. The output is functional. But the process and the criteria for success are closer to art than to engineering. The question is not just whether it works. It is whether it means something.

The Medium Is Code

Painters think about paint. Sculptors think about stone or metal or clay. Creative technologists think about code. Not as a tool for implementing designs, but as a material with its own properties, constraints, and possibilities. Code is unique among creative media because it is both the material and the machine that shapes it.

Taste Over Technique

Technical skill is necessary but not sufficient. The creative technologist also needs taste: the ability to distinguish between what is impressive and what is good. Taste is developed through exposure. Look at work outside your field. Study typography if you are an engineer. Study systems thinking if you are a designer. Read about architecture, music, film, and philosophy. The connections you draw between disciplines will be the source of your most original work.

Shipping as Practice

Creative technologists ship. This is what distinguishes them from artists who work with code. The work must exist in the world, accessible to real people on real devices. Shipping is not a compromise. It is part of the practice. The creative technologist's job is not to choose between art and engineering. It is to refuse the choice entirely and build things that honour both traditions simultaneously.