You make some excellent points here and your illustrations would drive me mad with envy if they didn’t make me giggle so much, but I’d emphasize the difference between raw data and usable knowledge. For me, it’s part of what separate Pro’s from Paying Punters – Paying Punters point and clap at the puppet show; Pro’s get themselves backstage and work out which string pulls which limb. I don’t think people need much more practice at remembering the Cool Bits from games and movies and TV shows, but almost everyone needs more practice in working out why they’re cool, what it is about that technical solution that made it better than another, how was it put together, and what was so compelling about its presentation: the What isn’t as important as the Why and How.

For instance, why did New-Monster-Every-Week one-or-two-episode morality play SciFi TV series like Star Trek and Doctor Who come up with the Transporter beam and the Tardis respectively? To what production problem was that the solution? Why didn’t they go with an expensive but heavily repeated sequence to get their protagonists to and from their weekly new locations, like Thunderbirds? The relative production costs of a single special effect shot compared to a three-minute model montage will tell you more than any retro-con backstory explanation.

So my addendum to your advice to budding devs is to take all the games, TV shows and movies they love, and see those finished works not as monolithic blocks of Cool, but as a consequence of a series of design, direction and production decisions, decisions that can be analysed and reverse-engineered. Steal from the very best, I say! Just learning a few of the technical terms used by screenwriters, storyboard artists, directors, coders, sound designers, composers, actors and developers will give you more insight than memorizing every line of dialogue in every episode of every season of every franchise of StarTrek. Technical language is a kind of toolkit that lets you build something new, not just repeat something old. Knowing every episode featuring the character Data is just, well…data.

Being able to analyse the Cool Bits doesn’t mean you appreciate them less, quite the reverse – it makes the Cool Bits cooler. As an example, take the famous lots-of-short-shots montage technique pioneered by Sergei Eisenstein. Every movie nerd will be able to tell you about the famous Odessa Steps sequence in The Battleship Potemkin, and most will know that Brian DePalma recreated it almost shot-for-for the train station shootout scene in The Untouchables (even the Great steal from the Best). The more I read about the critical theory that built up around Eisenstein’s technique, the more I appreciated his achievement, and dug the visual syntax of cinema, and how long and broad a shadow it casts on all subsequent movie and TV editing. But this was as nothing compared to the slack-jawed awe I felt when I found out that it was his work-around for a potentially show-stopping production problem: only very short lengths of filmstock were available at the time, so he invented a way of telling stories with very short shots. That’s not just smart, that’s flaming, strobing genius! Future developers, be inspired!

The bottom line is: with the game mechanics being the core, come up with a vision that others have not done before, and is fun to your target audience, so they would want to play your game and enjoy while doing so.