I hated math at school. I just hadn't found a problem worth caring about yet.
Most technical artists I know are self-taught in math. Some never felt the gap. Others hit it mid-career when the work got more complex: shader debugging, LOD budgets, performance tradeoffs that needed real justification. I had a good mentor who reignited the interest in me, because I genuinely hated it in high school.
Where it actually pays off
For me it showed up in three places: writing shaders, optimization, and building custom scripts and nodes for image processing and automated tools. All three involve parameters with mathematical shapes. Knowing whether you're working with a linear, squared, or exponential relationship changes how you approach the problem entirely.
Debugging a shader is different when you can reason about the equation rather than tweak values until it looks right. If the BRDF output looks wrong at grazing angles, knowing which term is responsible tells you exactly where to look. Without the math, you're guessing.
The most consistent payoff: when something breaks and you know why, you fix it faster and explain it clearly to whoever needs to hear it.
Where it doesn't
You don't need a degree. Most of what comes up in technical art is linear algebra and some calculus fundamentals: vectors, dot products, matrices, derivatives.
The value of deeper math also depends on the role. Rigging-heavy work is different from shaders-heavy work. Pipeline work leans more on scripting logic than graphics theory. It compounds fastest if you're working close to rendering.
If math feels like a wall: don't start with a textbook. Start with a problem you're curious about. The math sticks faster when there's something concrete to attach it to.
© 2026 Stefan Groenewoud. All views are my own, not those of my employer.