A Quote by Kim Jee-woon

Whatever it is that I thirst for in my current project tends to turn up in my following project. — © Kim Jee-woon
Whatever it is that I thirst for in my current project tends to turn up in my following project.
It depends on the project, what's happening that day on the project, at what stage were in on the project; it various from project to project and where we're needed.
I think it is important to be present in the places where you are working. It is not only about doing a project, but following the project through its construction.
When the government undertakes or approves a major project such as a dam or highway project, it must make sure the project's impacts, environmental and otherwise, are considered. In many cases, NEPA gives the public its only opportunity to be heard about the project's impact on their community.
I'm strictly a one-project-at-a-time kind of guy. If I came up with a compelling idea for a different book while working on a project, I'd probably abandon the first project and go with the new idea.
One of an actor's fears is that your current project could be your last project.
I never had a lot of ideas. I always have exactly one that is the next project; the idea of a project beyond that project is ludicrous.
I've been really lucky that I've kind of gotten to flow from project to project, because I find it's very important that when you're on a project, you are so invested in it.
I think my tendency when working is to try and find what's lacking in my current project and then tackle that in whatever I do next.
The way in which a society organizes the life of its members ... is one "project" of realization among others. But once the project has become operative in the basic institutions and relations, it tends to become exclusive and to determine the development of the society as a whole.
The primary purpose of software estimation is not to predict a project's outcome; it is to determine whether a project's targets are realistic enough to allow the project to be controlled to meet them.
I have a lot of alter-egos: I would love to be a back-up singer for someone someday. I have an electronic side-project. I have a '90s grunge side project; I have a piano project... I have this industrial, goth-electronic song, super creepy sounding, just really dark and dreary.
I try to just be open to what the next experience is and how it makes me feel, just reading a project, or trying to get involved with a project, or thinking about a project, and what particular emotional flavor that brings. To me, it's never really about planning the next thing, or the career arc. It's about investigating how I feel, from project to project, and finding things that I haven't explored and what that would be like.
Software projects fail for one of two general reasons: the project team lacks the knowledge to conduct a software project successfully, or the project team lacks the resolve to conduct a project effectively.
I can pretty much spend an entire week talking about how the writing process works, to be honest! It can really vary from project to project and is often dependent on when you're brought on board, the genre, the platform and the narrative desires of the project.
I'm no good at down-time. I panic slightly and then plan a project or set up a meeting about starting a project.
It's nothing. A school project. My go-to answer for anything. Staying out late? School project. Need extra money? School project.
This site uses cookies to ensure you get the best experience. More info...
Got it!