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. The only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…