3 ms·
Great video. Some quotes: "The core of skill of innovators is error-recovery not failure-avoidance." "Mastery in anything is a really good predictor of master
by dominik 18y ago
Great video. Some quotes:
"The core of skill of innovators is error-recovery not failure-avoidance."
"Mastery in anything is a really good predictor of mastery in the thing you want done."
"The proof of a portfolio versus the promise of the resume."
"We want somebody who's more interested than they are interesting."
"People who are interested are much more willing to work on the communication as a destination not as a source -- and breadth, a broad range of experience in the world is the thing that fuels that."
"Depth, breadth, communication, collaboration; of these four collaboration is the most important"
"Collaboration for Pixar means amplification -- the amplification you get by connecting up a bunch of human beings who are listening to each other, interested in each other, bring separate depth to the problem, bring breadth that gives them interest in the entire solution, allows them to communicate on multiple different levels: verbally, in writing, in feeling, in acting, in pictures, and in all of those ways finding the most articulate way to get a high-fidelity notion across to a broad range of people so they can each pull on the right lever."
- Gonsalu 18y agoThe theory is great for, as the talker said, innovative fields... For a programming business which needs, let's say, a Java programmer, I think it matters more (to the recruiter) that the programmer knows its fu well, than being very interested; basically, the theory doesn't quite apply to existing businesses which use common technology.
- arebop 18y agoI'm sure most Java recruiters agree with you. But, as a programmer myself, I've only met a handful of other programmers whose knowledge I'd value over their interested-ness. I'll probably never have the opportunity to hire such a person, so when I interview I look for competence and learning potential (curiousity, humility, ...). Also, I regard programming as a maximally innovative field. There's no reason in principle to do the same thing more than once in programming, and the practical reasons all seem to derive from a combination of mistakes and misfortune.