Skip to main content

On The Art Of Directing

Here is the thing: when a conductor raises that skinny chopstick of his (or hers), you don't see him or her actually play an instrument. You are, however, assuming that the person, who is responsible for the operations of the whole orchestra, is capable of playing at least one instrument. And I bet you are right. More than that, actually, many of them are indeed multi-instrumentalists and often quite capable solo performers.
Another thing - play of film directors. I bet they can act, most of them. And many of them are former or still performing actors, too.
Not when it comes to directing art, oh, no.
I suggest a simple test: take a book, any book, and put it on a table. Put an orange, apple, or an office toy basketball on top of it. Now give your art director a pencil and a sheet of paper and make him draw the book and the object on top of it in perspective. Forget the shading, just the wireframe (that's even better test).
And even better one would be to draw from imagination, without that improvised still-life.
How many of us can guess the outcome?
Right.
I see this problem as very much computer-related. It's the very essence of a common mistake of substituting the tool for an ability. Just like stringing some prerecorded loops in GarageBand does not make you a composer, your virtuosity of applying the drop shadow in Photoshop makes you neither an artist, nor even a graphic designer. It makes you a fraud, who got the job because you have a "creative vision" and "attention to details" and "people skills" and you "can get the job done".
And guess what?
It's OK.
It is, because you probably have all of the above, or you believe you do, which for me is just as good.
I do not have a problem with you directing me.
I do not have a problem with you telling me what to do.
The problem I have is with you telling me HOW to do it. You can tell your chauffeur where you want to go. You can even tell him, what route to take, scenic or highway. But for the sake of anything sacred to you, do NOT tell him how to switch gears.
Especially if you never drove a stick shift.

P.S. if you care about your job security, however, you should perform the aforementioned drawing test in your imagination. You already know the result, right?
P.P.S. Good thing nobody ever reads this blog, too.

Popular posts from this blog

Who is running MacAddict forums?

I normally hate to complain, but, being a happy subscriber to the magazine for some time now, feel like I do need to express a concern about my recent experience with MacAddict forums section of the web site. Due to some server misbehavior, I had to re-register, my old profile disappeared, while I was updating it. My new profile was assign a label "n00b" (None Of Our Business, if I am not mistaken. This is some way to welcome a new member to the MacAddict community). It could've been cute, but it isn't. And I don't think, it was intended to be: from the post of "Scott": "...using tables for layout...is for lame-ass n00bs..." I have read several more posts in the "Web Design and Development" forum, which, for some reason, was for a couple of days named "George" (the name is back to normal now; but here is how forum moderator "Gipetto" reacted when he was asked about this oddity: "...poop, it blew me away tha...

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen , and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying. Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay. P.S. Resolved the cache issue with .htaccess file: FileETag None Header unset ETag Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"  everything now works a lot livelier. P.P.S. Why is Blo...