RyanWe're on the cusp of deploying a new, standard path template for the show. Which means everyone gets one (1) chance to have the impossible argument - what order should the fields go in?
A resource I've used to grow as a #python developer is pyvideo.org, which hosts recordings of Python conference tasks.
There are thousands of talks about a wide array of subjects. This linked thread from my old account is about the talks I feel have learned from.
https://mograph.social/users/yantor3d/statuses/109413390506074424
Ryan (@[email protected])
1/ A resource I've used to grow as a #python developer is pyvideo.org, which hosts recordings of Python conference tasks. There are thousands of talks about a wide array of subjects. This thread will be about the talks I feel have learned from. #techArt
Are you attending #SIGGRAPH and are interested in working at #Laika? The studio is hosting a mixer on Tuesday - RSVP using the link below!
https://www.eventbrite.co.uk/e/laika-siggraph-2024-mixer-tickets-948479336227
"My shot is broken."
"Which one?"
"My shot."
"Which one?"
"My shot!"
"What shot number!?"
"Oh, XYZ.ABC."
If I had a nickle for every time I had this conversation with a junior TD:
Them: "Ryan, I found a bug! Here is the stack trace!"
Me: "Great! File a ticket, follow the stack trace, fix the bug, send me the MR."
Them: "..."
Recently I stumbled across the notify-send command which, when paired with sleep or at, allows you to trigger a deferred notification. So I can, for example, remind myself in five minutes to do the next step of a deploy without having to remember to remember.
And for a #vfx #pipelineTD whose attention is constantly getting pulled in multiple directions, this feels like it will be a game changer.
2/2
As I was writing this thread I realized that I'm essentially proposing an recursive or layered asset management model, where the contents of a workspace are tracked local to the workspace and only the final result goes into the main system.
As the saying goes, "there is no problem in computer science that cannot be solved by another layer of indirection, but this usually ends up causing other problems."
The job of a #pipelineTD is to make those problems small and manageable.
4/4
I'm just a #pipelineTD, standing in front of #maya #USD, asking it to export a useBackground shader correctly. Or at all.
RyanWho among us hasn't wanted to tell the animators, "should these commands be ignored, a disaster beyond your imagination will occur?" and then drop a chandelier on them when they do?
You'd think that "as a lead, I want to be able to configure which checks run before publishing, and with what severity" wouldn't inspire so much feature creep, but boy, that escalated quickly.