Growing up in a time when the status quo of console gaming was just beginning to take shape, one can vividly remember the time when I saw a plumber on screen and was told that a certain "Mario" was me, and I was to control him in order to "win the princess." Much more amazing to me then was that when I pressed a button, that Mario guy would do something! It would jump! At that time, it felt like I was a god that had ultimate power - even though it was only a plumber with no other purpose in life but to get the princess by jumping over and above square bricks.
Fast forward to today's world, and I find myself living in a reality not so distant from my past - the industry of technology. In other words, software is the main thread that binds together most of what I do. The bits and bytes have become ubiquitous, and an internet connection is already something akin to air - you don't notice it when it's around, but when it's gone, you'd think the whole world was conspiring against you. That said, the software in the world basically take up two mantras - the one being the native code, and the other being the platform.
You'll notice this because as widespread a language may be, more often than not there will be platforms available that further the features of the native code. And yes, it's true that they get you places. However, like how Mario can just jump into a brick and break it, so will a platform act the same.
A platform is a platform is a platform - it does help you get to places, but if you build your skills (and ultimately, your career/business) around it, it will eventually fall apart - leaving you to fall to the depths of whatever is down there.
Perhaps this is why I had apprehensions in using platforms so much. However, it's come to my realization that I've been building on platforms for a while now, though I never really realized it as such. Point is, the more specialized, deep, and abstract a platform is, the weaker will it's staying power be.
Now, the decision to use one is a relative one - it's best to weigh the future and present returns before taking a big leap and clicking on "Sign up!".
Fast forward to today's world, and I find myself living in a reality not so distant from my past - the industry of technology. In other words, software is the main thread that binds together most of what I do. The bits and bytes have become ubiquitous, and an internet connection is already something akin to air - you don't notice it when it's around, but when it's gone, you'd think the whole world was conspiring against you. That said, the software in the world basically take up two mantras - the one being the native code, and the other being the platform.
You'll notice this because as widespread a language may be, more often than not there will be platforms available that further the features of the native code. And yes, it's true that they get you places. However, like how Mario can just jump into a brick and break it, so will a platform act the same.
A platform is a platform is a platform - it does help you get to places, but if you build your skills (and ultimately, your career/business) around it, it will eventually fall apart - leaving you to fall to the depths of whatever is down there.
Perhaps this is why I had apprehensions in using platforms so much. However, it's come to my realization that I've been building on platforms for a while now, though I never really realized it as such. Point is, the more specialized, deep, and abstract a platform is, the weaker will it's staying power be.
Now, the decision to use one is a relative one - it's best to weigh the future and present returns before taking a big leap and clicking on "Sign up!".
No comments:
Post a Comment