Tuck Abbott

WORK HISTORY

EDUCATION

SKILLS

ABOUT TUCK ABBOTT

What I Do:Bridge Art + Engineering- From being one of the first tech artists at a startup that grew an early startup into a CG Content team that served a team of >100 to contributing to franchises with over a decade of history, I can find ways to make new connections and solutions on teams with complex challenges.Make Work More Fun- Using Python, C++, C#, Unreal Blueprints, Houdini, MAXScript, SQLite, cloud-hosted build experience, Perforce\'s CLI, and more, I\'m able to automate processes and create workflows that cut iteration times from hours to seconds.Scale Content (And Keep It Fast!)- From Forza Motorsport\'s weather systems and expansive vehicle and tracks library, HoloLens AR/VR applications running on tight hardware constraints, large-scale synthetic data generation with LiDAR/Radar rendering, I\'m able to balance fidelity within a wide range of runtime budgets to meet project needs. Have led projects around performance in many contexts to help guide engineers and artists to be performance-aware in their day-to-day.Learn and Teach- I\'ve managed teams as large as 14 and pride myself on mentorship, context-sharing, and changing organizational culture in a way that advocates for myself and my team members while being cognizant of business needs. I realize that a team\'s best work is done in an environment that supports their working styles-How I Work- I consider Tech Art to be professional learning. I have a passion, drive, and talent for efficiently diving into unfamiliar systems and looking at things with fresh eyes, and I trust that the learning process leads to good outcomes- Context is king. Asking who needs this, why they need it, what would make it awesome, and getting specific about the answers will show the right path forward- Multidisciplinar-ily (it\'s a word now). Across artists, software devs, producers, ML engineers, and more, the best solutions occur when we think together- Obvious and Elegant > Magic and Complicated: Tech art shouldn\'t be magic. Simple UIs, clear documentation, and consistency across tooling make for better environments. Tools shouldn\'t be magic- they enable users to make the magic happen.All opinions shared here are my own.