Archive for March, 2008

Mar 31 2008

I Am Klang

Published by saalon under Blogging on Blogging

Blog spam has changed a lot since the last time I let trackbacks hit my site. In the days when I used Movable Type, spam catching software was so onerous to use that I just shut the whole comment/pingback/trackback thing off and didn’t look back. After my – I think – 3rd install of Wordpress on my 3rd provider I was looking around for a stat tracking plugin and the use of it required getting a Wordpress API key. This same API key, I discovered, could be used for Akismet, a spam-catching plugin that protected you from having to moderate or delete every false pingback and comment the net could throw at you.

So I installed it and let it run. The spam I used to get on my old blog was completely unrelated to my site. Lots of the same porn/Cialis/Instant Money things that showed up on Usenet and in your e-mail box. That’s still out there, but a new, odder type of spam has appeared.

You know how when you search for something on Google, a lot of what you get are those annoying link metasites that have a snip of content from real sites along with links to them? Well, there are more of those than I’d ever imagined on subjects like health food (not so odd) and mathematics (really, really strange). A lot of these don’t even have a ton of ads on them, making me wonder why they would install a bot and Wordpress just to capture newly posted articles so they can put up things like:

Saalon Muyo placed an observative post today on “Reading is Overrated” – A Portrait of a TV Guide PodcastHere’s a quick excerpt … com crew as they provide inside scoop, offbeat opinions and answers to your questions about the latest entertainment headlines, the hottest TV shows, the newest m ovies and the biggest celebrities. … It at times infuriating, it spent too long talking about empty reality shows like Big Brother and too little time on deeper dramas like The Wire, but it was a good t ime

Le What? Obserative? Why, thank you.

Anyway, they usually get the name of the site or – sometimes – the name of me, the poster, correct. Ok, they get my online nick right, not so much my real name. Today, on the post I just put up, I got this:

Klang wrote an interesting post today on

Here’s a quick excerpt

Klang. I am Klang. Yes, there is a blank after “on”, so I guess their bot is as unsure of my post’s subject as my readers are.

Couldn’t I at least have been Kang? Or even Krang?

No responses yet

Mar 31 2008

The Science of Art

Published by saalon under Coding, Creating

I’m finding that my writing process and coding process is more similar than previously imagined. This shouldn’t be a surprise. I’m not the only one that’s gone on and on about the similarities between artistic and design processes. Maybe it isn’t really a surprise, or a revelation, but an unexpected clarification.

When I write, I spend most of my time thinking and not writing. My actual time spent putting words onto electronic paper is minimal compared to how long I spend pacing around my office moving pieces around inside my head. In fact, when I do it right, the actual writing part of writing is as close to effortless as work can get. That’s one of the reasons I don’t like to write before knowing what I’m writing; when I do, it feels too much like work. The other reason is that I hate editing. I’ll talk about that later.

I’ve now worked on a handful of end to end projects in my engineering job, which is enough to start noticing patterns. I’m finding (shock) that I spend a very long time organizing the overall picture of what I’m doing in my head (or sometimes in a notebook) before writing more than a few liens of code or defining a few empty methods. It leaves me feeling unproductive for the early part of my project, as well as afraid I wouldn’t finish on time. How was I going to get the coding done with half of my time already spent?

Yet in every case, once I had a good model of what it was I was doing, the actual coding part of the project only hit a snag if I needed to figure out how to technically implement something. Like this: I know I want to find this part of an XML document, but I don’t know the correct method to accomplish it. I also was spending much less time than expected having to debug what I had built, both because I had worked out a number of the logic problems before coding, and because the time spent thinking had produced relatively clean code that was easy to fix.

I doubt I’m the only person who uses a long Thought Before Code spin-up process, or even that I’m in the minority. At least, I doubt this is a rare practice amongst successful programmers. The unsuccessful ones rarely have consistent processes, which is probably what makes them unsuccessful. Still, I wasn’t expecting such a clean similarity between how I write stories and how I write code.

Then I thought about it further, and it makes a kind of sense I should have seen before. When I go through my writing spin-up, it’s not the language or the flow of a conversation that I work out before writing. It’s the way the larger, more abstract pieces are going to interact. It’s how the motivations of a character are going to bounce them into or off of other characters, how all of those characters are aligned in such a way that what results is a clean, smooth narrative.

What I’m working out are all of the pieces that must exist behind the story for it to be the thing that I see in my head. The delicate connections between this strand and that, between event and response, between motivation and action. It’s a kind of architecture, really.

When I was in my first photography class, my teacher described the most important part of taking any picture: pre-visualization. Don’t press the button, he said, until you can see the picture that will result in your head. This wasn’t just looking through the viewfinder and lining up the framing or pulling focus or deciding how far to zoom. It was more than that. It was visualizing the way you wanted the picture to look by understanding how the camera would see the scene.

A photographer needed to put himself inside of his camera. They needed to internalize how light levels and shutter speed and aperture size and framing and zoom and depth of field and all of that would interact to produce an actual, physical photograph. More, they also needed to internalize how another person would then see that photograph, to know how, once that photograph was set, the elements of it would draw the eye to one place or another.

They needed to think through the entire photograph, from how they saw the scene, to how the camera would see the scene to how that final picture would give to the audience exactly the sense the photographer had before depressing the button.

Once again, there’s an element of architecture there. When you’re building something, you need to understand how the stresses and supports and elements of your final work are going to interact. Like when kids who are good with Legos are about to build: What pieces do I have? What colors? How can those pieces connect in such a way to become the castle I have in my head? If you just start chucking Legos onto the base – like I did – you’d end up ripping up half of the thing to get it working, and even then, you might not have the time and energy to get through it.

A lot of people talk about how programming is an art, but not enough people talk about how art is a science. The art is the detail, it’s the delicate hows that make up your work. The art of a photograph is the specific way your eye follows the curve of a railing and the shadow it casts towards the face of your subject, and more specifically, how that image is crafted to make you feel. The science of it is internalizing how light exposes on silver nitrate, and how the settings on your lens will leave one part in focus but another pleasantly blurred. You can shoot from the hip with art, and a lot of the time you probably should. But the science? Spending some time working that out may be for the best.

Or perhaps I just feel unproductive in those early days and need to justify it. If so, consider this bit of writing a resounding success.

No responses yet

Mar 26 2008

Action Blunder

Published by saalon under Creating

You have a hero love and a villain we hate. The hero has kicked many asses on his way to the villain, and the villain has kicked even more. If you’ve done your job properly, the fight between the hero and the villain is – at best – evenly matched. Better yet, the hero is outmatched enough that we don’t see how he can win this one. Now it’s time for the throwdown.

You’ve done most of the heavy lifting. Nearly all of the really difficult work is behind you. Yet even though this fight is the payoff you’ve worked so hard to earn, you can’t get cocky. One trial remains: the resolution of your final battle. Step lightly. Disaster awaits the unwary.

Today, I come to warn you of one of the most dangerous traps. A resolution to battle that is sure to leave your audience bitter and dissatisfied. They may not recognize which misstep is responsible, but they will not be pleased. This pitfall is a combat technique which properly executed cannot be defeated.

Look back to an earlier point in your story. At any point does either your hero’s mentor or the villain demonstrate something that when properly executed cannot be defeated? Did you insert this scene so that either:

  1. Your hero can catch the villain in it to finally succeed?
  2. Your villain or hero can use it, only to see it miraculously defeated before their eyes?

If so, repent while there is still time. There are few reasons for any technique that properly executed cannot be defeated to exist in your story. There are even fewer reasons for them to serve as a plot device in your final battle. The first reason may seem more incorrect than the second. After all, we’ve all seen too many battles where a hero is pounded only to suddenly win with a well timed Crane Kick to not cringe a little at it.The second, though? What’s so bad about that?

The only thing worse than inserting a Super Move into your story and using it is inserting a Super Move and then running kryptonite over it it in a cheap attempt to create tension. If you’ve decided a move that properly executed cannot be defeated has a place in your story, go all the way with it. Make the move as cool as it is unstoppable and make us cheer when the villain is pounded into the ground with it. Using it at all is a bad idea in most situations, but is still superior to showing us a BFG in Act One only to have the villain laugh it off in Act Three. Trust me, our tension has not increased. Only our frustration.

If your hero is unable to defeat the villain without something that properly executed cannot be defeated, perhaps your story was meant to be a tragedy.

One response so far

Mar 25 2008

Security Through Presumptuousness

Published by saalon under Coding

The problem with trying to convince someone that your security model is dangerous is that, unless you work in something obvious like banking, any scenario you try to throw out as an example leaves you sounding like Cassandra. Worse, as people question why this extra level of security might be needed, you might feel compelled to start throwing out half-baked worst case scenarios. If there’s not some obvious, immediate use to breaking into your system, people’s immediate reaction is to say “So they get a password they shouldn’t. Then what?”

It doesn’t matter if someone can think of a scenario. That you didn’t consider a malicious application of your system or network is no deterrent to those who will. One mistake people make with security is to assume the limit of their own imagination relates in any way to their exposure to actual threat. This is especially perilous when your own faulty assumptions put people paying you for your expertise at risk.

This is not cause to go overboard, but simply to be sensible. Opting for a clearly flawed security model because you don’t think someone has any reason to break it is folly. In most cases anonymous FTP is no danger if the right fences are put around it, but that doesn’t stop many hosting providers from refusing to offer it. They don’t do this because someone gaining access through anonymous FTP is likely, but because the worst case scenario is an unacceptable risk to them. What is the worst case scenario? Something worse than the worst thing you considered.

Requiring insane, impossible to remember passwords is not what I’m talking about. How about something simple like sending a user name and password through clear-text e-mail, but not allowing your users to change either? Or assuming your third party providers have a security policy that’s as tight as your own, and leaving yourself vulnerable if you’re wrong? Or not having a thorough and up to date audit of what any given permission actually opens up across your systems, figuring that users will only open things they’re supposed to?

If people sending you a check are relying on you to be stable and secure, don’t allow arrogance to convince you that the things you haven’t thought of are unimportant. Don’t allow yourself to believe that you are not important or big enough for someone to bother breaking down the door. You’ll always make mistakes and you’ll always miss something. Do yourself, and your users, the favor of at least checking both the doors and the windows before you go to sleep. One way or another, your security prowess is irrelevant in the face of human stupidity and malice. Crackers aren’t relying on your imagination when deciding what to do with your system. There’s always a bigger fish.

No responses yet

Mar 24 2008

Fat Is Back

Published by saalon under Doing

Portfolio.com recently posted an interesting article about the resurgence of really bad for you food, focusing on the strategy CKE (the parent company of Hardee’s and Carl’s Jr.) has adopted over the past half decade. Go read it, but if you want to read this first, let me discuss the article in short.

Fast food took a bunch of hard knocks when things like Super Size Me and Fast Food Nation tore down the facade that the industry had built around its dietary offerings. The line had always been that their food was absolutely nutritionally sound, even if it wasn’t health food. Now people were realizing that junk food was bad for you (shock!) and wanted to get something healthy at the same price they were getting crap.

While chains like McDonald’s began phasing out things like Supersize options, CKE looked at the market and decided people didn’t really want health food, they just wanted to know it was available. Rather than follow the pack and start offering wraps, they did the exact opposite and wheeled out some truly monstrous burgers with a caloric content over the recommended daily amount for the entire day.

CKE’s thesis, which the article doesn’t challenge, is that the fast food chains bowing to market pressure made the wrong decision. People want to eat, as they call them “decadent burgers.” The only reason you’d put a salad or yogurt thing on your menu is so you, the hungry alpha male, can bring your wife without her complaining too much. This is thesis the other fast food chains have come to accept, leading to competing death-burgers like Wendy’s Baconator and Burger King’s Triple Whopper. People don’t want to be told what to eat, the line goes, and thus will rally to the cry of morbity on a bun and support it with their wallets.

This thesis is supported with evidence of CKE’s increasing same store sales, and it’s a compelling argument. In fact, I think there is a lot of truth there: a certain group of people do want to eat crap. They enjoy it, and are offended by the idea of a group of dietary elitists supported by the media taking away their right to murder themselves. To these people, an ad campaign that tells people that the worst food for you is right here is a breath of fresh air. At McDonalds in the 90’s, they were living in denial, pretending their Supersized Big Mac was good for them so they could fit in with a culture controlled by a health-conscious bourgeois. Now they were enabled – nay, encouraged – to purchase items called Thickburger or Baconator with pride.

I’d like to offer a counterargument. Not to the entire idea, because – as I said – it’s not entirely wrong. Where I suspect the CKE gluttony-as-a-strategy case doesn’t hold is in its suggestion that people who say they want health food don’t actually want it. CKE offers as evidence their poor salad sales, and steps right up to the line of mocking people who think health food sells.

All this proves is that the people already interested in buying from fast food places like Carl’s Jr. aren’t buying vegetables. I doubt this is evidence of anything other than that people don’t come to Carl’s Jr. for anything other than meat, cheese and fried potatoes. A more thorough analysis would probably prove two things.

First, the people who are conscious of what they put into their bodies simply do not eat at fast food joints regularly – if at all. Second, that even when people who do take care to eat healthy things go to a fast food joint, they are either not interested in healthy food at that moment, or take a look at the sickly salad being offered at too high a price and decide to indulge themselves.

I’m speaking from some experience here. I eat oatmeal or healthy cereal for breakfast most mornings. I try to get the right amount of fiber in my diet every day. I’ve cut down on meat and I keep an eye on my sodium intake. If possible, I eat one meal comprised entirely (or mostly) of vegetables a day.

When I step into a McDonald’s, that’s out the window. I get one of the most unhealthy things on the menu: McNuggets. I add in a big thing of fries, too, because I like to dip them in that Hot Mustard concoction they careful parcel out. I don’t step into a place like McDonald’s unless full-on crap is what I’m craving. That’s supremely anecdotal, I realize, but my attitude is rare. I’ll concede that a lot of people talk the talk without walking the walk when it comes to health food. We’re a fairly hypocritical culture.

Still, I’m willing to bet that of the people who say they want health food, more of them mean it than CKE’s gloating tone would lead you to believe. I’m also willing to bet some of those people, when going into Hardee’s or Carl’s Jr., purchase the Monster Thickburger with glee, not because the presence of a salad on the menu makes them feel better, but because that Thickburger is the only reason they went to the place at all. They had their salad, but now they want an unhealthy, heart-stopping treat.

(As a side note, there’s another significant factor at work here: price. I’ll need to talk about that in a separate article, but suffice to say the food to price ratio has a lot to do with fast food’s popularity, and shouldn’t be ignored.)

Which, in a lot of ways, validates CKE’s marketing strategy. They’re right, even if they overstate their case: The people who would be interested in eating at Hardy’s aren’t going to go ga-ga over a turkey wrap. They want meat, and if possible, they want it topped with something fried. McDonald’s marketing themselves as a health food chain is absurd. Their food sucks, whether it’s healthy or not. Take away the junk fried part and all you’ve got left is tasteless crap.

Running an advertisement where a girl in a bikini eats a huge hamburger is delivering your potential customers their favorite lie: Eating nothing but 5,000 calorie meals will make more – and hotter – girls want to sleep with them.

No responses yet

Mar 20 2008

On Programming Examples

Published by saalon under Coding

If there’s a failure common to many programming sites, it’s the lack of useful examples. This goes both for those high level overview examples you see at the beginning of a chapter and for the actual code samples provided a few pages later. This is a problem for me, since I need context in order to really learn something. Neither seeing a block of code with no explanation of what it’s supposed to be used for in a real system nor reading a superficial example of functionality so simple it does effectively nothing stick with me. I see these examples falling into one of two categories.

The first attempts to turn every programming lesson, no matter how complicated, into a “Hello, World!” example. Need to read from an XML file? Great! Here’s how to load a file with one node, choose the one node that’s already there and read from it! Fun! What you won’t learn is how to use actual XML files where there are lots of elements with a crazy mix of child nodes, inner text and attributes. Want to find out how to read specific information from an XML file based on some kind of criteria? Sorry, no, because all we’re going to give you for an example is:

<Library>
  <Books>
    <Book>
      <Title>The Client</Title>
      <Author>John Grishom</Author>
    </Book>
  </Books>
</Library>

When most XML files look more like this:

<Library Name="Moon Public Library" ZipCode="15108">
  <Books Status="Available">
    <Book Author="John Grisham" DateReceived="3/18/2008">The Client</Book>
    <Book Author="Dan Simmons" DateReceived="3/17/2008">Angels and Demons</Book>
  </Books>
  <Books Status="Checked Out">
    <Book Author="Guy Gabriel Kay" DateCheckedOut="3/10/2008">The Summer Tree</Book>
    <Book Author="Michael Crichton" DateCheckedOut="3/12/2008">Jruassic Park</Book>
  </Books>
</Library>

Only they look worse are even less logical.

The second category try to help you understand the theory behind something by providing a fatuous real world analogy. You know, like, how the best way to describe object oriented programming is to compare a class to a blueprint and an object to the car you make with the blueprint, or to say that you can make a car class, and that a Honda inherits the attributes of a car but adds its own things, like comfy seats and an iPod connector, but you can also have a Pinto inherit from a car as well, but add completely different features, such as ExplodesOnImpact. Which would all be great if I, or anyone reading an entry level programming book, was planning on programming a computer to build cars of every make and model.

Might I suggest that if you require a description of object oriented programming that eschews any reference to things you might actually do on a computer this might be too early to study the topic? I’m not saying you need to have three years of experience here. Just that you might want to stick to programming concepts that you can understand in terms of things you might do with a programming language. Let’s try my own example:

You’re writing Pac-Man, but you want to make it Object Oriented because everything must be designed using this paradigm to be correct. Now, you want 4 ghosts, but you want them to all behave slightly differently. You want Blinky to directly attack Pac-Man, and you want Clyde to always try and cut him off. You could code each ghost separately, but there would be a lot of repeated code. They all basically navigate the maze in the same way, and none of them should be able to eat power-pellets, but they should all kill Pac-Man. So you could make a Ghost class that has the generic behaviors, like movement and speed and all that jazz. Then you can make, say, a Blinky class that inherits the Ghost class, but adds an Attack method that figures out the shortest distance between it and Pac-Man. Instant inheritance!

What most examples lack is good context. What’s that Library example supposed to apply to? Are most people looking for examples on XML because they are in a position to create idealistically clean XML, or are they trying to figure out how to parse the monstrous crap pile that their server at work is dumping on them? You may have shown me what the basic structure of XML is with the example, but not any idea of how I’m supposed to use it. Your example is so much simpler than anything I’ll actually encounter that I can’t apply your example to the real world. And the car analogy? Please, bury it somewhere in the middle of the woods. No one reading it is going to get one of those exclamation points appearing over their head from the sudden shock of understanding you’ve delivered to them.

We program in order to accomplish some task. If you want to teach something, put your example in the context of an actual task so that when I go back to my actual job I can actually frakking apply it.

No responses yet

Mar 19 2008

Arthur C. Clarke

Published by saalon under Watching

I can’t claim to have been a huge fan.  I think you need read more than one of someone’s books and seen one of their movies before you can claim to be a superfan, even if that book is one of your favorite ever.  Still, a giant among men is a giant among men even if I can only point to his footprints as evidence of his passing and not my own experience.

Arthur C. Clarke passed away yesterday at the age of 90, an age we are all more likely to reach because of minds like his.  Certainly Clarke’s main contributions were not scientific but speculative, but without a bold imagination able to grasp the current state of technology while not being bound by it, the brilliant men and women who make things happen would have less to spark their own imaginations.  In the world of science fiction, Clarke was a colossus.

He worked in a time when the field had no shortage of great minds, yet still he managed to distinguish himself among them.  His novel Childhood’s End is a classic, even if people inspired by it managed only to steal the first half.  The second half remains entirely his, and it’s here that the challenging brilliance of the novel lies.  And 2001: A Space Odyssey is the granddaddy of modern filmed science fiction, even if – once again – people steal the look and feel but leave its difficult-to-grasp ending alone.  Even when he confused, he still inspired.

It’s difficult to lose someone, especially someone of his caliber.  Let’s remember, though, that we had him with us for 90 years;  his voice was not silenced too early nor were his words ignored.  He lived, I hope, a happy life.  For someone who has brought so much joy to others, it’s the least the world could have done.

No responses yet

Mar 18 2008

Exploitation Now

Published by saalon under Watching

The great thing about 70’s exploitation flicks is that the reasons you should see them are the exact same reasons you shouldn’t. Forget the nuanced discussions of plot, theme and character you have after you watch Magnolia or Blade Runner. Pop in The Hills Have Eyes and the guy who likes it is going to love up the same damn things the guy who hates it decries. The symmetry is beautiful.

For instance, take Fight For Your Life, made the year before I was born. Here are some of the reasons given to convince me to see the film:

  • A gun is pointed directly at a baby’s head.
  • A child is beaten to death with a rock.
  • Lots of nudity.
  • An insanely, absurdly racist villain.

Can you imagine the reasons someone might give for hating this one?

The exploitation genre was meant to be abrasive. It pushed boundaries simply because they hadn’t been pushed for decades. As the Hayes Code receded into memory, directors wanted to try and use the medium to shock their audiences a little, to address issues most film was too timid to address head on. Think about Fight For Your Life for a second. By 1977 America was already learning to pretend that racism didn’t exist. More artistic, sensitive portrayals of racism married the ugliness to their work delicately. Fight For Your Life had no qualms about giving us a villain who talked about African Americans the way far too many people still did around their dinner tables when no one was there to overhear.

I can’t defend the exploitation genre’s intentions. Even if directors talked high-mindedly about what they were trying to expose in America, and even if they sort of meant it, the real draw was the voyeuristic thrill that accompanies seeing insane shit playing out on your screen. That said, there’s something to be said for work that doesn’t flinch from the vileness of our world. There can be something to be learned from the experience, even if education never crossed the filmmaker’s minds. A good exploitation film can be cathartic, and a bad one can still be an awful lot of fun.

Where modern entries in the genre fail is in their attempt to dress up the old exploitation flicks with deeper themes and character development. Suddenly, it’s no longer a simple formula. The guys who hate babies having guns pointed at them in principle may excuse the film for being “about something,” and those who came for the shocks are going to feel cheated by the cushioning those shocks receive when they’re dressed up with extra plot.

The exploitation films of the 70’s triumphed due to an utter lack of pretension. The film was a guy driving really fast in a really macho car who runs into naked chicks and troublesome cops, or a family of mutated, cannibalistic murders who come upon a poor, helpless family. That was it. The social commentary, when it was there, was subtle; it was a good sear and just the right amount of salt and pepper on an already meaty, bloody – but cheap – steak. Try to dress it up with some kind of mustard brandy sauce, and all you’ve got is a shitty steak that doesn’t know its place.

No responses yet

Mar 17 2008

“This movie needs way more gay”

Published by saalon under Randomness

Heh heh.

No responses yet

Mar 16 2008

How I Learned to Stop Caring and Love the Verse

Published by saalon under Creating

This is the third article in a series inspired by Paul Lockhart’s essay “A Mathematician’s Lament.” It is a meditation on Art, Mathematics and Education. The first part, “Why Them Kids Don’t Learn Nothing,” is primarily about education. The second part, “If Triangles Could Fly,” talks about art as a process of discovery, and this third part is a story of my first experiences with poetry.

 

The impression we are given is of something very cold and highly technical, that no one could possibly understand— a self-fulfilling prophesy if there ever was one.

- Paul Lockhart, “A Mathematician’s Lament”

It wasn’t the only time this happened, but it was the most absurd. I was somewhere in the middle of 11th grade, sitting in my advanced track English class. We were reading and discussing poetry. By this point, poetry was already the bane of my existence, and what was passing for discussion in class was the biggest reason. The poem under the microscope at the point this story gets interesting was some Sylvia Plath thing that talked about a gargoyle and may have had some “slick with rain” imagery going on as well. I can’t remember.

The way it worked was simple. Someone was called upon to read the poem. They did, in that halting, uncomfortable way someone reads something they don’t understand. Then the teacher asked the, “What did that poem mean?” question. No one would answer it, so the teacher would narrow down the question, aiming for the answer she already had written down on her lesson plan. “When she talked about the rain-slick gargoyle, what was she saying?”

No one in the class had given a single reaction to this poem yet. No one had even shown much interest in it. Yet here we were, being asked to pick out a single metaphor from the work as a whole. Some students reached into the clouds and pulled out a few random answers, until the teacher got bored with it all and just told us what the damned gargoyle in the damned rain meant and tried to move on.

Of course, I didn’t let her. “How do you know that’s what it means?” I asked. There’s probably one of me in every English class, laying in wait with our subjective viewpoint and our theories of literary relativity. In her defense, my teacher was genial about these interruptions, and for a few minutes we went back and forth, her telling me she just knew and me saying she couldn’t, unless she was hiding the author’s notebook back there somewhere.

We weren’t alone. My 11th grade advanced English class occasionally joined forces with the senior, AP level English class to talk poetry together. The 12th grade teacher, who to this point had been sitting at one of the desks quietly, suddenly stood up, berated me for being disrespectful to my teacher, and stormed out.

Later, I was called to that 12th grade teacher’s class where I was told that she was sick of people acting like literature wasn’t a science, and that there weren’t right and wrong answers in the field. I had joined the ranks of those troublemakers who wanted to discuss writing, and from that point forward my grades in that class dropped from A’s and B’s to C’s and D’s.

This was how I learned to hate writing.

If teaching is reduced to mere data transmission, if there is no sharing of excitement and wonder, if teachers themselves are passive recipients of information and not creators of new ideas, what hope is there for their students?

- Paul Lockhart, “A Mathematician’s Lament”

Only, I didn’t.

What happened in my mind through high school was a form of literary schizophrenia. I loved to read, and nothing in school ever got me to stop. Reading was something I learned from my family, not school, and so school had no power over it. I also really enjoyed writing, but the only kind of writing I was asked to do in school I was bad at. If you had asked me at any point during school what I thought of writing, I’d have said I hated it and I was going to become a programmer. At the same time, I was starting my school’s first literary magazine and writing for it. What those English classes did, I think, was convince me I wasn’t any good at it. For most people, that eventually leads to “I don’t want to do it,” too. It may have with me, if I hadn’t gotten lucky.

The casualty of my high school English education was poetry. I never really read it prior to having it assigned in class, and nothing about the way it was taught to me gave me a taste for it. Unlike prose, which I loved independently from school, poetry was ripe for the I’m No Good=I Don’t Like It equation. I didn’t understand it, and while I was sure my teachers weren’t right about the meaning of the stuff they were putting in front of me, I didn’t have the tools to find my own meaning. I also didn’t have the interest. Thus, poetry sucked.

Why aren’t we giving our students a chance to even hear about these things, let alone giving them an opportunity to opinions, and reactions?

- Paul Lockhart, “A Mathematician’s Lament”

When Paul Lockhart discusses the failure of our mathematics program, he talks a lot about how we don’t give our kids the chance to discuss the problems, to react to the solutions and to offer their own opinions. The rote transmission of information, the memorization of that information and then the regurgitation of it onto tests is what convinces people that they don’t like something because they don’t understand it.

I didn’t like poetry because I never learned an appreciation for it. I was never allowed to react to it, or to wrestle with its own particular intersections of form and intent. Being a good reader isn’t really something you can teach, per se. Neither is being a good writer. Learning to express yourself in a specific form, and how to understand someone else’s work in that same form, is a constant process. You get better at it the more you do it, and in my experience you never get best at it. There’s always a higher rung on the ladder. The only way to find it is to read and write more. And the only way you’re ever going to do that is to first learn how to enjoy it.

I never really read a poem in high school, and the only time I wrote one was when I was told “Write a sonnet.” Knowing nothing about sonnets save their meter, I produced what I can only imagine was a lifeless, awful piece of verse. The only thing I knew to do with a sonnet was to look at the number of lines and pick out that the analogy in that specific poem was the flower being the man’s lover.

Yet, when I went home and finished the fourth book of The Wheel of Time, I spent hours tearing it apart, talking about the scenes I thought were powerful and about what I thought would happen next. I didn’t talk about plot structure or chart out that stupid narrative pyramid, nor did I always use words like foreshadowing and dramatic irony, but I knew what worked in that story and, more importantly, I knew why. Because I called up my friends and I debated about it.

‘No society would ever reduce such a beautiful and meaningful art form to something so mindless and trivial; no culture could be so cruel to its children as to deprive them of such a natural, satisfying means of human expression. How absurd!’

- Paul Lockhart, “A Mathematician’s Lament”

The trick, I learned much later, was to realize that the teaching had been flawed and not my ability. I shouldn’t even call it a trick, because it took me almost a decade to really understand that. In fact, long after I decided my English teachers were full of it and that I could write if I damned well wanted to, I still let the lingering anger at verse stick with me. I had my own, personal feelings on prose that overrode the reduction of it a formula containing metaphor, symbolism, man vs. nature conflict and third person omniscient viewpoint. I had nothing of the kind for poetry, so the trivialization of it became what the form was, to me. I knew they were full of it, yet I still bought into their crap when it came to verse.

Finally, after years of prodding by my friends who hadn’t been so tainted, I’m coming around. I’m reading Bukowski and liking it. I’m even thinking about what it means. That makes me lucky. Most people never challenge their school-borne assumptions of a subject, and I can’t blame them. What stimuli do we have outside of school that would cause us to reexamine something and see if the reason we didn’t like it was because it wasn’t for us, or because we had been never been allowed to learn what it was?

That’s got me thinking. Have we reached a point when we need to teach our children not to care what their teachers say? I had a lot of good teachers, so that can’t be true, yet I only learned to love poetry after I stripped what my English instructors taught me of any authority. School makes noise about wanting to teach critical thinking skills for the Real World, and in that they have have inadvertently succeeded. If kids are going to come out of school having learned something, it’s going to have to start with more students able to look at a D on their Literature paper and decide if it was because they didn’t understand the assignment, or because they did.

No responses yet

Next »