Plan for future growth

For team growth one of the most important things is how do you plan to make your team future ready. This article is a guideline anyone can use to make themselves or their team future ready.

Software industry keeps evolving. And so everyone part of this industry needs to learn to predict, plan and adapt to the newer advances in the respective fields. I feel predicting the future (based on facts) will help you plan better.

Here are the simple guidelines one can follow:

Keep track of major sources of information in your field

This will keep you updated with new releases. For e.g if you an Android Engineer the information sources you can follow are https://android-developers.googleblog.com/,  https://medium.com/androiddevelopers.

Know how new releases are rated by the engineers

This will help you know how fast the new technology will get adopted. For this you can follow public forums of those technologies, weekly/monthly newsletter, Slack channel, StackOverFlow channels and similar others. You can get links to these on the official website for the technology.

Keep track of any existing similar technologies

This will help you know which one to pick when time comes. For e.g in Android there are multiple approaches that can be used to implement similar thing. Knowing pros/cons of all these technologies will help you make a better decision.

Follow the experts in your fields

This will help you learn from their experiences. For e.g in Android you can follow top Android GDEs (Google Developer Experts) of the world, frequent contributors to Android world and similar such folks.

Research and understand the kind of problem the new release solves

This will help you plan whether the new release will make your product better and whether it should be introduced. 

Track the timelines of actual releases

This will help you plan for the new releases. Once you know which technology to adapt knowing the release timelines and pace of adoption will help you get trained for it.


Hope this will help you to plan better.
Location: India

Comments

Post a Comment

Popular posts from this blog

Fragment Lifecycle

Image
Just like Activities, Fragments also manages its own lifecycle. Though these lifecycle callbacks are a bit different than activity’s callbacks they exist for the similar reason as that of activity’s callback. Fragment manages two different lifecycles. One for the fragment instance and other for the view shown in the fragment. Having different lifecycle for fragment’s view is useful in the situations where the work should be performed only when view exists. Points to note: Fragment lifecycle call-backs are similar to Activity’s lifecycle. More important they are dependent on Activity’ state. Fragment manages 2 different lifecycles - Instance and View. Fragment callbacks are: onAttach, onCreate, onCreateView, onViewCreated, onViewStateRestored, onStart, onResume, onPause, onStop, onDestroyView, onDestroy, onDetach Fragment state is saved before onStop for API level less than 28 while in API level 28 and above its saved after onStop method. i.e In API level 28 or above devices its safe to...
Read more

AndroidManifest

Image
One of the most important components of your project. Stays in the root directory of the project source. This is used to describe essential information about the app to Android Build Tools, Android OS and Google Play. Most important things for which AndroidManifest is used: To declare app’s package name: Used by Android build tools to map code entities and to map it with applicationId defined in build.gradle To declare different app components: Include all activities, services, broadcast receivers, and content providers To declare app permissions: Helps in accessing specific restricted by System or other apps. To declare hardware and software features: Used to decide which device can app be installed into Package name and application ID Example <?xml version="1.0" encoding="utf-8"?>        <manifest            xmlns:android="http://schemas.android.com/apk/res/android"           package="co...
Read more

Activity Lifecycle

Image
To let Android System interact with Application different methods are defined by the system which communicate different states of the activity to the application. Those methods/states are called as Lifecycle Callbacks. Activity can go into different combination of these states. In the code each callback is used to understand the state in which the activity is in and accordingly perform different operations. Let’s discuss different activity callbacks and what each of them represent in real life scenarios. You will find each section explained with the 3 labels. Let us see what each label represents: Called: It will tell you when is this method called. Implement: What should be implemented in this method. State: What is the state of activity from user's perspective.                         onCreate() Called: This is the first callback received in Activity which is called as soon as the system creates the Activity. Implement: Used ...
Read more