Frameworks come-and-go. There’s nothing you can do. But one thing you can do is – adapt. And if you don’t, you’ll be forgotten like your framework/tools. Most of us fear new stuff. We fear change. Adaptation is very easy if you can overcome the fear of it. It is not only true for the framework but also for programming languages/libraries/tools etc. I will refer all these together as “X” in this writing.
Step 1: Quick Start
My first step is to read and to go through quick start/first step guide. Generally, all major official documentation provide this type of quick start guideline which also includes example code. I start implementing (coding) right away with a small application that pops up into my head at that moment and tries out some features of the X.
Doing this gives me an idea of X am trying to learn. Moreover, it gives me confidence that I am “making” things with this new X. I am like – “WOW!!! Cool it is working!” which eventually helps me to go forward. It takes me a couple of hours to get familiar with the X.
Step 2: Dive In
After spending a couple of hours of basic quick start, I START DOING real project/task…
I do not try to learn everything before I start. While following quick start guide, I try to understand why and what am doing each thing mentioned there. I do not write any single character of code that I do not understand. I think it is one of the essential things. Initially, I do not copy paste code, instead try to write, reason and modify it as I go.
Follow Convention: I’m very strict about the convention and best practices. Hence, I read and follow their best practices and convention guideline as I start coding. However, that does not mean that you should never go off the book. But that should be very rare and exceptional case, and you will know when you have to do that.
Read Documentation: I read official documentation. It becomes my bible while I code. I try not to watch video tutorials. To my observation, tutorial helps you to learn quickly and easily but kills your technical reading capability. It affects severely when you try to develop advanced stuff since that advanced stuff is not available in tutorials. On the other hand, if you are familiar with the documentation, you will be able to figure out how to do that or where to look at for that. You will know how to use resources like Google search, stack overflow and online articles quickly when you are stuck.
To sum up, I do not restrict myself to any language/framework/tools/library. I try to adapt, and I feel these tricks help me to set off efficiently.
Lastly, one of the keys to Apple Inc.’s success is – adaptation. They not only adapt but also frequently kill their own popular product and present newer one. Apple killed their Macintosh, killed iPod, even killed headphone port! Here is a video from PolyMatter which describes this matter quite adequately. They know – technological changes are inevitable. So, they bring the changes themselves instead of following the trends. They become the trendsetter and not the trend follower.