Project Motivation Quotes

I only get involved with projects as a producer if I feel creatively inspired.

I've just always loved really good projects. The things that draw me into a new project have very little to do with genre and have more to do with the characters I'll be playing, the people I'll get to work with and things like that.

I do always try and do work that I'm going to be interested in talking about when it's released.

We realized we weren't really using Odeo, we weren't investing our own time creating podcasts. We were building a tool that was a great idea for some other people. That's a dangerous way to go because if you don't actually use it yourself and love it, then you aren't going to be as fully invested in it from the start. That's what leads you to doing side projects.

I have to be absolutely drawn to the project. If you're ashamed or bored by it at the beginning, it's going to be a pretty nightmarish thing.

I wouldn't say I worked with these people because I was looking for a particular vocal sound. I worked with them because I loved what they had done before-and because they really wanted to work with me.

Hopefully, by the time I do a project, I already have a true understanding and love of what I'm about to do because if I don't, I'm not going to work on that project. I really want to have those connections so I can be truthful to the emotional aspect of what I have to deliver for the story.

I didn't make 'Wild Bill' because I wanted to become a director; I just wanted to make 'Wild Bill.'

I'm just happy to do projects I'm passionate about.

I'd argue that everybody wants to do something that matters, and the fact that Linux has had a huge impact on the tech market and is used virtually everywhere is obviously very personally satisfying. I think programming is fun, and the community around the kernel is great, but a project has to be relevant too.

I always need a couple of highlights to really spark the passion for a project.

Before I find myself in the middle of a project, I want to make sure it is the kind of thing that keeps me excited for two years. Otherwise, it will be very difficult to push the proverbial rock up the proverbial mountain.

You never undertake a project because you think other people will like it - because that way lies madness - but rather because you believe in it.

You pick a project. You think, 'I can succeed at this. I can help them. I can make it so that they'll want to call me again the next time.'

For me to do a project - I have a pretty successful solo career, so - for me to even want to do Primus, it had to be a creative step forward.

For me personally, to hop onboard and use the amazing success and blessings in my life to pull off something like the 30/30 Project is awesome.

But now I really don't want to work unless I really, really care about a project.

I like to do projects I feel some connection to.

I don't want to take up a project for the sake of it. I want to work and follow my passion, and not anything else.

I'm not in the business of adapting things that are popular for the sake of just getting it on the screen. I think there has to be a vital reason.

I started working on OpenBSD, and many earlier projects, because I have always felt that vendor systems were not designed for quality.

Before I start a project, I always ask myself the following question. Why is this book worth a year of my life? There needs to be something about the theme, the technique, or the research that makes the time spent on it worthwhile.

The only way I can work is if I care and am passionate about a project, so the challenge is to find projects that I feel that way about.

We really love all sports, but we don't think in the long term. The reason we did Kingpin was because there was a script we really liked and we saw the possibilities.

Projects don't need to be special for me to sign up, but I do need them to have something that speaks to me in some way.