Book Review: Tales From Development Hell (New Updated Edition): The Greatest Movies Never Made?

Tales From Development Hell (New Updated Edition): The Greatest Movies Never Made?
By David Hughes

ISBN-10: 0857687239
ISBN-13: 978-0857687234

PROS:

  • An insider’s look at Hollywood’s movie machine and how it often takes years – or over a decade to make a film.
  • Snappy, exciting, writing style that engages as well as informs.
  • Lots of juicy, oddball, interesting information.
  • The author’s personal stories help flesh out the truth of the book.

CONS:

  • Occasional information overload can be distracting.
  • Complexity of the Hollywood system could have used some flowcharts.
  • You’ll want to punch Hollywood in the face.

SUMMARY: An indispensable book for anyone that wants to know how Hollywood works (and doesn’t work), and why a lot of films never happen – or turn out poorly.

Read more

How A Helpful Letter Produced A Firestorm

OK, clearly I missed the whole Shea Gunther drama, so let me recap.

  • Monday, Mr. Gunther sends out an email to people who applied to a job for a cleantech news site, listing criticisms and giving advice on the job search process. It hit the newsat the Guardian.
  • This hit the Gakwer network, who posted it in a rather negative context.
  • This produced what we technically call a “shitstorm” and Mr. Gunther ended up with a predictable amount of trolls and insults – as well as people praising him. Though the usual dogpile of would-be internet tough guys/gals is odd to see as this is about job search advice, and I don’t get why it’d get people that riled up.  Mr. Gunther summarizes the experience here.
  • You can read his entire list of advice in this Scribd document.

I’ve read it Know what? It’s good advice. In fact, I advise that anyone read it, as his tips are accurate, if skewed towards the writing positions in question. Mr. Gunther lists a whole lot of trends that are troublesome, gives advice, and makes good points about what people do wrong.

Read more

Ask A Progeek: What DO I bring to the position?

What’s our question this week?

How do you answer “What do you bring to the position” in a job interview without reciting the job posting OR going too off track?  What’s the right balance of requirements and outside details?

I don’t know anyone that really enjoys answering this question (OK, I kind of do, but I like a challenge).  The problem with saying “what do I bring to the position?” is that we’re not sure if we’re answering the question, or answering the question for the person asking it, or . . . well, you get an idea.

Really, we don’t know what kind of questions we’re answering or who we’re answering them for.  We’ve just been asked “what do we bring” after filling out a lot of forms and reading a laundry list of requirements (or, just as bad, no list).

The first thing to do is to realize that the question is coming and prepare.  If you’re shocked this comes up, then you’re not ready.

The second thing is to review the position – not just the requirements, not just what people said it is, but what it really is.  Do your research, read up, etc.  If you’ve been in a profession for awhile you probably know it pretty intimately.

With this review, then compose your answers for “what do you bring to this position?” ahead of time.  Make sure it answers what you can really do for the real position.  Feel free to work in a few bullet points or catchphrases if you think it’s needed, but make sure it’s a real answer – a real in-context answer.

Third, prepare to be pre-emptive on this question.  If an opportunity comes up to show what you can do, use it – just don’t blatantly spit out a bunch of catchphrases or prepared statements.  If someone asks about specific experience, focus on the stuff you’ve done and know relevant to the job – in context (as I always say).  Make sure you’re answering the question ahead of time.

If you do it right, you’ll possibly spare your poor interviewer from having to ask “what do you bring to the position,” because they’re probably tired of asking it and getting a verbal tsunami of an answer (or blank looks).

Fourth, work this into your personal branding – very big for us professional geeks.  Is there a chance to show that what you bring to the position is, well, you?  Can you use your meekness as an edge in answering (or preemptively answering) that question.

So the question’s coming.  Be ready.

– Steven Savage