I hate running. I’m terrible at it. I have an awkward form
that causes my knees and back to hurt after I do it for any considerable time. I
wouldn’t say I have a “runner’s body” by any stretch of the imagination. I’m also pretty slow, something that makes
running suck for a person as overtly competitive as I am. Yesterday, I ran my
first half marathon. I finished in the top third of all finishers at my race,
and averaged 30-45 seconds per mile faster than my training paces. By all accounts,
I did a pretty good job, and I certainly did better than all of the people who
decided not to run 13.1 miles yesterday morning. So then why, considering the
above, do I still struggle to identify myself as “a runner?”
The Army does a poor job of marksmanship training. When I
was issued my service pistol, I sat through classes for hours learning the
names of all of the component parts. Then I learned how to assemble and
disassemble the weapon. Then I saw several illustrations on what a proper sight
picture looks like and where my point of aim needed to be. When I finally took
my pistol to the range, I had received all of the marksmanship instruction I
was going to get. I fired at my first
targets at the full 40m range, just like I was supposed to. To say I hit a
third of my shots would be very generous. For the shots that I missed, I had no
way of knowing what errors I was making, so I couldn’t correct them. It was
like I had been taught to swim by watching a very detailed DVD on swimming, and
then I dove from a boat into the middle of a lake and had to swim my way to
shore. Eventually, over many months and attempts, I became an expert marksman
with my pistol, but not because my taught experience taught me what I need to
know. When I taught my wife to shoot, I had her engage targets at 2m, then at
5m, then at 10m. She became familiar with the fundamentals of her shooting, and
every bullet hit the target. We were able to correct her deficiencies while
still building confidence that she was a “shooter.” Eventually, she was back at
the 40m line shooting with me. The difference between her experience and mine
is that she never identified herself as a failure- she hit the target most of
the times she shot at it, so she kept trying to learn.
I’m really zeroing in on an idea that ran through the last
section of the diSessa reading. On page 64, diSessa says, “We need especially
to remind ourselves that simple and easy uses…not just grand accomplishes,
accumulate as part of intellectually revolutions such as new literacies.” If we
discount all the miles of training runs I completed, and the race times of
everyone except the few elite finishers of my half marathon yesterday, simply because
they aren’t spectacular, we fail to recognize and capitalize on 2000-plus imposter
“non-runners” supporting and growing the running culture. Us “imposters” may soon
drop out due to the lack of community support, and the realization that they
will never be an elite runner. Similarly, if we only concern ourselves with
beautiful, aesthetic projects, and ignore and discard the simple, possibly
flawed creations of beginning programmers, many newcomers who realize they will
never create the next Facebook or Windows may decide to quit. By ignoring or
discounting their contributions, we are doing an injustice- not just to those
fledgling new programmers, but to the computing world altogether.
Yes! I think the identity aspect is crucial. And as you note it our ideas of identity often come about through either a specific picture of what the identity looks like or our own experiences in trying to meet the picture. Am I only a programmer if I have a published app? or if I'm male, highly intelligent in math/science and anti-social? (although I think this stereotype is changing somewhat, thank goodness). More than ever we value the polished product and person which hides the actual process of creating or becoming. From this it seems we both need to change the picture people have of programming/programmers and while teaching, emphasize the process and those little steps.
ReplyDeleteExactly my point. When my son took his first steps, I told everyone who would listen and some people who wouldn't. My mother posted the video to her social media page with the exclamation, "We have a Walker!" Any parent with kids of walking age knows my jubilation isn't unique. And no one who sees the teetering, shaky first steps of a toddler criticizes that that isn't "really walking." Yet we do that all the time in school.
ReplyDeleteDoes each of us remember with pride and accomplishment when we first programmed our computers to display "Hello, World!"? If not, why not? If not because "Hello World" isn't "really programming," then perhaps we need to have a hard look in the mirror.
Yes, to everything! A few years ago my brother bought me the book "Lean In" and your post made me think of it. Sheryl Sandberg (COO Facebook) describes a notion that following a test - girls are more likely to say they did poorly on it than boys are. There's this automatic feeling of self-doubt - even for girls that consistently do a good job. I wonder if there is a way to accomplish your wife's experience with learning to target shoot with girls learning to code. Programming involves a lot of failures and perhaps it is this natural self-doubt that is greatly affecting the amount of women in computer science. Maybe it is an infusion of computational thinking into areas in which girls do feel confident (a la Wolz) that may help make the smaller accomplishments more motivating/inspiring.
ReplyDeleteI agree that changing the idea of what it means to be a programmer is key to making computational thinking a literacy. Every learner should be exposed to programming through as many disciplines as possible. However, at some point, people will drop out and begin identifying themselves as "non-programmers". Will that leave us with all the males who are most interested in math and science? Does lowering the entry point change who will ultimately find the field fascinating and stick with it? (Even if it doesn't though, we should definitely still make it as inclusive as possible from an early stage).
ReplyDeleteOn a slightly related note, I feel like there are some fields that stand out to me as attempting to make themselves distinct from the layperson. The most notable one that comes to mind is the business world. I don't know much about business or finance, but from what I have heard, there are a lot of "buzz words" and distinct terminology used to... keep less business-smart people away? ensure that business-smart people will continue to have jobs? Obviously, I'm not in business, so this might be totally wrong. But I wonder if medicine does the same thing: attempt to use more complex language than needed in order to distance itself from its clients. Because otherwise, we'd be out of a job. Would a similar step-down of terminology change the world of programming? Would that be good or bad?