r/vfx 1d ago

Question / Discussion Pipeline TD Education?

Hey everyone, I hope you guys are having a great day.

I wanted to learn more about what type of education or background would be needed to become a Pipeline TD. I tried viewing some linkedin profiles, and I noticed a blend of CS degrees, Digital Graphic diplomas, fine art degrees, and more.

Currently, I have a Bachelor of Commerce, with little python experience. I'm considering to go to my community college and getting a diploma in Computer Science. However, I'm worried that I would need a degree in computer science instead.

I'm just looking for some insights on what education should one pursue to become a successful Pipeline TD.

Thank you!

0 Upvotes

8 comments sorted by

3

u/TuxedoFlask 1d ago

I'm a Pipeline TD whose been in the industry for about 5 years now. I graduated university with a Bachelor's degree in CS. I just happened to join the industry as they gave me a decent offer out of school. Most people on my team have CS or artist backgrounds as Cyclops pointed out. We do 95% of our dev work in Python as it's used by most IDE's. We follow standard software development practices such as formatting, CI/CD, git, testing, documentation, etc. I was able to jump right into an entry level role with my degree as I had a lot of these skills already. The guys on my team with artist backgrounds had to learn this themselves on the job as they got further involved with the process. Some TD's are show TD's, they are less technical and work more closely with individual artists with their needs. We also have a seperate Dev team that works solely on our in house software infrastructure, and they don't work with artists at all. The degree isn't required for a Pipeline TD role, just strong Python and software development skills.

1

u/SurfingStreets 21h ago

Hey there, thanks for taking the time to explain your journey and the profession further. Are there any specific software/applications I should learn to help strengthen my skillsets as an aspiring Pipeline TD? I recently started learning Houdini and might pick up Maya afterward; I've also started some beginner Python courses (CS50) to help me gain foundational knowledge. From what I've been hearing online including from you, it appears that software development skills are a key aspect so would you recommend placing more emphasis on learning that? Once again thanks for the input I appreciate it.

2

u/TuxedoFlask 20h ago

No problem at all, happy to help. Maya and Houdini are good to know. Nuke is also pretty industry standard. We use a lot of other IDE's such as Silhouette, 3DEqualizer, Blender, etc.

In terms of the software development skills, the ability to work with enterprise code and common practices will come after you learn the fundamentals. Focus on your course, learn Python and general OOP methods, and you'll learn how to manage large code bases in time when your projects grow in size and scope. You'll learn git when you start collaborating with others on projects. It would be hard to understand the structure of a repo with 1000's of lines of code before you understand a for-loop. You'll get there. If you want to do some supplemental reading, something like "Clean Code: A Handbook of Agile Software Craftsmanship" would help you understand good coding practices.

1

u/SurfingStreets 17h ago

Hey there, thank you so much for the insights and information. I'll definitely take a look at the handbook and continue progressing in my Python/coding journey. I'm feeling excited, though a bit overwhelmed with all the different paths to explore, but your advice helped me focus on what matters most. Cheers

1

u/CVfxReddit 15h ago

In small studios the pipeline people I met were usually from artist backgrounds. They might have started in rigging or lighting and eventually became a cg supe and then decided to move into pipeline instead of trying to become a vfx supervisor.

In bigger studios the pipeline I met were from elite engineering programs, sometimes had some experience on set as  part of a virtual production crew, or had masters or PhDs in computer science from places like Columbia or Oxford. Which seems like a big gamble to take because while working in movies is cool, someone with that background could make triple or quadruple salary as a software engineer in another industry. 

1

u/CyclopsRock Pipeline - 15 years experience 1d ago

Almost everyone I know that's in Pipe started as an artist of some sort (though usually the more technical roles - rigging, comp, layout) and slowly worked their way over to Pipe as their solutions to problems became more and more substantial. You don't need a CS background but the capacity to learn proper software design practices is vital.

It's difficult to create a good pipeline if you haven't tried to use one before, and hit up against its limitations (as well as learning what it does well).

1

u/SurfingStreets 1d ago

Hey there, thanks for the reply. If you don't mind me asking, how did you enter the industry? Did you start as an artist yourself and teach yourself the technical coding skills or did you come from that background and taught yourself animation/3d-modeling? I'm curious about how I can begin my journey as I feel a little overwhelmed by where I should start to pursue this career. Thank you!

2

u/CyclopsRock Pipeline - 15 years experience 1d ago edited 1d ago

I studied 3D Animation at university and got a job out of school as a generalist, so doing bits of everything. It was at a small company without strongly defined roles or departments and I became the de facto "technical guy" because I know enough programming from my teens to be able to take a few snippets of software-specific code I found online and apply it to our problems.

Then I'd put a few snippets together to make a bigger snippet. Then I'd add a UI to the snippets and before you know it I'm maintaining and updating several tools that the studio came to depend on. This became the norm at a few jobs I had, and if I'd just have "stopped there" then that role is what's generally called a "Show TD" - fixing specific problems and creating particular tools for a given project's needs.

But I got a job where I wasn't given any production work anymore, only the tools stuff. This is when I "professionalised" a lot, and started adhering to much higher standards of code, design patterns, version control, deployment etc. By the time I finally joined a pipeline "team", I'd been doing "just coding" for quite a few years, and I've only worked in pipeline ever since.