true. having not developed a keen eye, you have to apply common sense to any advice, especially that which purports to know. a novel? no problem.
see, i can tell a story in fiction form. telling the story isn't an issue, it's telling an effective story *in a script format* that needs to clock in at or around a certain length that i'm trying to learn about. like anyone else i think, i'm looking at advice here and there and everywhere and seeing what i can see and agree with, looking for common denominators, hints and tips, particular craft elements, and how the business is run, etc.. so these books and articles and such serve merely as a way to cut through years of trial and error. no, i doubt some guy's formula will work for me any more than some guy's horse betting system will rake in cash hand over fist, but it took this guy years to develop it and there's likely something worthwhile to take away from it considering i know dick about screenwriting. (remember, i don't know how to write a screenplay per se, but that's far removed from knowing how to tell a story.)
were i to start today, this is what i'd do (and under the idea that i'm not trying to reinvent the wheel, just trying to tell a story within the parametres): i would get myself some 3 x 5 cards that serves for scenes and jot down what scenes i have already in conjunction with an outline that expands on those scenes. i'm not reaching for the stars on the first several ideas by any means. the first idea is a simple low-budget horror script, of which i can't count how many i've watched (i can't get enough of B horror for some dumb reason), so it shouldn't be difficult finding one that's got roughly the same tone i'm looking to achieve. it'll be a decent movie ~ i don't plan on writing stupid shit so why pick out a bad movie?
anyway, i'll indeed sit down and compare the movie with a beatsheet just to see how well the two compare. i'll count scenes. i'll maybe even time scenes, or at least pay attention to their general length in relation to one another. i'll do all this so i know and not with the idea of copying, rather to get a feel and make sure the advice from these gurus just all wasn't a ton of bullshit. i'll do that with several movies and will read the scripts if those are available.
and there's one thing i've got to admit right now: i know me, and i know that i'm not going to be one of those guys that reads a hundred scripts before penning a single word. i'll knock out about twenty of the movies i admire (if i can find those scripts) with an eye towards specific things. imo, 'network' should be required reading. my goal there would be to concentrate on dialogue (not to say it isn't a great story. and besides for some 'well, bob, as you know...' exposition early on, it's the perfect example of the difference between great dialogue v. realistic dialogue. that is, regular people aren't usually that witty, talk that fast or instill that much intellectual concepts in their average speech right off the top of their heads. compare that dialogue with 'the godfather' and there's an ocean of difference.) i'll read something else to focus on action. then read a few samples of each for comparison's sake. and with all of them i'll want to pay attention to character description and introductions, scene set-ups, the flow of the action, scene direction (if any). i'm also of the mind that i don't want necessarily a script that's been written and directed by the same guy. i'm sure 'pulp fiction' is very entertaining to read, but i also have to wonder how much of that would be applicable to the spec script i'm trying to get out, know what i mean? and i want to be sure i'm looking at specs, not shooting drafts.
but at some point i'll have to actually begin, you know, writing a screenplay! at some time you'll have the basic format down along with some nice stylistic things to do. i'm not sure reading another fifty screenplays will help me with format. i'm sure it wouldn't hurt, though i'm not sure what i'd gain would be a dealmaker, either. it's like those people who read voraciously and yet still can't produce a story worth reading. what's the point of all that 'research' if you just can't do the job? what, is another hundred books to your credit going to magickally make your writing all come together? probably not. there's got to be a cut-off point where you feel confident enough to start the job.
i'll give you an example: recently i started a new job building humvee engines. they wouldn't even let me do the first thing until i spent two daze observing. honestly, they could have started me off after about half an hour after walking through the door. i've started more complicated jobs after being shown once and the guy standing over me for a minute to make sure i could do the job. two different cut-off points, same result. mileage will vary from person to person.
the idea is if i know what i'm looking for then i don't have to slog through six months of material waiting for inspirations and epiphanies. not that it's not an ongoing learning process and those twenty are the only ones i'll ever read, not by a long shot, just that to get me up and running with a real sense of how to pull things off i don't need a thousand examples. does that sound too over-confident?
i'm nowhere near there yet. i've got the rest of this book to read, i want to compare it to another, i've the scripts to knock out, and a story to add meat to in the meanwhile. after a few scripts are banged out to my satisfaction, i'll promptly panic and forget the first thing i should do, and i'll be asking a lot of basic questions which, if those books are worth their weight, i should already know the answers to.
if i can't do forty scenes, i sure can't do sixty, though, eh? lol. i've a few movies here and there and i like to *think* i have some kind of sense of scope, so if i know it's a slam-bam-thank-you-ma'am rom-com, i'll likely be down in that forty range as opposed to a sweeping mob epic that spans the decades.