Skip to main content

Who Will You Be Tomorrow?

Growth is not something we’re really instilled with when we’re growing up, ironically enough.

Flashbacks in movies to the protagonist’s youth tend to show a mini-version of the adult, full of nods to their grown-up selves. Here you can see the people they will grow into already taking shape. Often, the younger versions of characters in a flashback will be almost identical to the older in personality. This is especially true in group flashbacks.

Growth, we’re told over and over, is a straight line up. The kind of growth we’re not exposed to is growth that shoots off in directions you never anticipated. We aren’t told to expect and never to embrace changes in yourself that alter you so fundamentally you aren’t even recognizable any longer to your younger self.

When growth surprises us, we’re taken off guard. We’re afraid.

There is so little left of the boy I was not that long ago. Who I’ve become is so much more than older. The changes in my understanding of the world, in how I hold my own image in my mind, in my religion and values are so different from the trajectory as a child, which were so different than myself as a teenager, so different from my younger adult self, so different from myself today.

There is going to be a man wearing some of my clothes, married to my wife, father to my son in a few years time. He’s going to hold a driver’s license with his face and my name. This man will share my birthday and social security number, but I cannot be sure that this man is going to be me and this is simultaneously frightening and exciting.

We’re all like the phoenix, the mythical bird that bursts in a blazing fire at the end of each life, only to be reborn from the ashes. But we can do this so much more often.

I’m reminded of a common phrase: kill your heroes. Not literally, of course. This is meant to understand that your heroes are nothing more than normal people. Hold them on your level. If we apply this to ourselves, I think we can learn to let go of the preconceived notions we build about who we fundamentally are as people. We can learn to let the people we are today fade away, like a suit that no longer fits. We can allow ourselves to effortlessly slip into our new selves.

Who never know who you’re going to be.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro