I hate posting about Pixar stories because the Steve Jobs omerta still lives strong in me... but what the hell. I couldn't watch the video because I'm on a train - however, I worked at Pixar from 2002 - 2008, so I'm pretty sure I know exactly what this video is about. This story was legendary inside the studio - I never thought it would get outside the gates. In some ways, the fact that this had happened in the past,…
Have you read The Pixar Touch? If so - what did you think? The feeling I got from the book, was that Steve Jobs was really bad when it came to the vision for Pixar. He had 0 faith in their movie making abilities, but the Pixar team managed to 'wag the dog' long enough for them to actually produce movies and validate their reason for being to the rest of the world.
Pixar Studio Stories: The Movie Vanishes
31–33 of 33 posts
Re: Pixar Studio Stories: The Movie Vanishes
#32Earlier quoted context omitted.
Have you read The Pixar Touch? If so - what did you think? The feeling I got from the book, was that Steve Jobs was really bad when it came to the vision for Pixar. He had 0 faith in their movie making abilities, but the Pixar team managed to 'wag the dog' long enough for them to actually produce movies and validate their reason for being to the rest of the world.
The guy wrote million dollar checks every year for 10 years to keep that company running. If that's not a big leap of faith ( losing money for a decade?!) then what do you consider faith.
But the folks at Pixar wanted to make movies. So what they did was convince him that by doing work on movies and commercials, they could advertise the capabilities of their tools.
Eventually, they were able to buy enough time to get their work recognized and the Toy Story deal going which validated their vision and won Steve Jobs over to the movie studio idea.
Re: Pixar Studio Stories: The Movie Vanishes
#33Earlier quoted context omitted.
It's not Ebola, and these are all people who worked on Toy Story. John Carmack isn't going to leak Doom 4. I'm pretty sure he can be trusted with that one. Why would you give away your life's work to some thieving bastard on the internet who you'd never met and didn't care about you, anyway?
Not John Carmack, but what about a junior dev? What about the QA people? How far down the chain do you go with who gets to take a copy home? On a large operation you can't rule out the bitter ex-employee factor either.
If you have a guy working for you who would leak something you're working on, the solution isn't to not allow people to take things home, it's to fire people who would harm your company.