Listen before changing anything
I first try to understand what the artist is trying to achieve, what changed recently, and what kind of problem they are actually facing.
About
My background is in Nuke compositing, but my current direction is Pipeline / ATD-oriented: artist support, Nuke/Python tools, workflow troubleshooting, and practical production technology habits.
I care about tools and fixes artists can trust. My compositing background helps me understand why a technical issue matters: not as an abstract bug, but as something that can block a shot, break a deadline, or make an artist afraid to change the setup.
Support mindset
I first try to understand what the artist is trying to achieve, what changed recently, and what kind of problem they are actually facing.
I look beyond the visible symptom: paths, versions, dependencies, color settings, render setup, environment mismatches, or workflow gaps.
I prefer small, reversible changes that preserve the artist’s work instead of broad changes that create new risk.
When the same issue appears more than once, I try to turn it into clearer documentation, a checklist, a shared setup, or a tool.
Nuke, NukeX, ACES, EXR workflows, roto/paint, tracking, keying, cleanup, element integration, Mocha Pro, and review-driven delivery.
Python, Nuke Python API, PySide2/PySide6, Qt UI development, JSON, GitHub, documentation, tool configuration, and safe defaults.
Artist troubleshooting, Maya-to-Nuke handoffs, folder structures, naming, versioning, render setup, file paths, and clear explanations.
Java, object-oriented programming, data structures coursework, command-line basics, testing/documentation habits, and ongoing CS study.
Computer Science coursework, including Java/OOP and data structures.
Diploma in Compositing with Honours.
BA in Digital Art, Visual Effects, with honours.