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 operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world. Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove: All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through. Where did they all go? My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access.   I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I cou...