Geek Alert

Following up on [last night’s post](http://johnaugust.com/archives/2009/show-your-work), it occurs to me that designing and programming for the web also has an aspect of showing your work. Nearly every browser lets you “View Source,” showing how the page was constructed…up to a point.

For example, if you View Source on the new [Answer Finder](http://johnaugust.com/answers) I built, you can see the JavaScript (and jQuery) that drives the menu and shows/hides the various sections.

What you can’t see is the PHP on the server that generated those sections. In my case, this is a good thing, because the PHP is so awful and kludgy that I can’t explain or defend why it works.

So to make that one page, I’m relying on a bunch of technologies with vastly different levels of transparency.

The “transparent” technologies are available for anyone interested in looking. And that’s mostly good: Peeking beneath the hood is a great way to learn how a technology works. I often find myself opening the CSS for sites I like to see how they’re constructed. ((Keep in mind that you can learn bad habits this way.))

I’m classifying HTML as semi-transparent because so much of the HTML you see when you “View Source” for a site is generated by scripts running on the server, and it’s not automatically clear how or why. WordPress, for example, mixes in at least four parts (Header, Content, Footer and Sidebar) to make any given page. Someone familiar with WordPress might be able to deduce a basic structure, and figure out which parts were generated by The Loop. But in some cases it’s arbitrary. For example, the category links at the bottom of most pages on this site could be hard-coded or generated on the fly, and you wouldn’t be able to tell.

While you can find a lot of information about the images used on a site, including where they’re stored, you don’t necessarily know how they were generated. The chart above, for example, is a .png made from a snapshot of a Numbers document.

In the fully-opaque category are PHP and MySQL, who do most of the heavy lifting for the site but are completely insulated from the user.

Traditionally, programmers have been able to disappear behind the opacity of a compiler. Designers could hide behind the printing or manufacturing process. With the web, the process behind the product is much more visible.

(End of Geek Alert)
=====
The same thing is happening to movies. Not too long ago, a movie came into existence in popular culture just shortly before its release, when the first ads and trailers started running. I didn’t know anything about Die Hard before I saw a trailer. I saw The Blair Witch Project without any idea who made it or how.

Now, long before the marketing begins — before production even begins — details of projects spill across the internet for consumption and criticism. Scripts leak. Photographers sneak pictures of the set, or the costumes. The omission of a giant squid becomes the focal point of conversation for a movie that doesn’t yet exist.

For movies and television, I’m not sure we’re better off “showing the work” in advance.

I appreciate reading American Cinematographer to see how Robert Elswit lights There Will Be Blood, but I don’t read those articles before seeing the movie, lest I get too distracted by those details when I watch it. Likewise, I wish I didn’t know what I know about Terminator: Salvation or Dollhouse. It’s not insider knowledge, but rather the media reporting on the media.

This isn’t transparency, an invitation to come look inside. It’s forced exposure. It’s uncomfortable, and by nature we try to avoid uncomfortable things.