What to learn and what not to
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
- Bacon 1) Beer 2) Sunshine After that is up to you.
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
sumitskothari wrote:
Can anyone suggest how should I prioritize the things.
For professional development or personnal interest? Idealy find the one that ranks high on both scales. Are you aiming to become an expert on one topic or have decent knowledge on many? Priorities depends on what you want and only you know that.
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
Personally, I prioritize things according to my current situation. I focus on topics that are related to my tasks. It would be good for me to learn mobile development but as of now, I'm not able to apply it on my work. Learning many concepts/technologies is good if you have a lot of time doing it, but there's a chance that you might forget them later on because you were not able to apply it. So choose those that you think you can apply later on, and then gradually increase your learning on other topics while applying those that you have already learned.
Signature construction in progress. Sorry for the inconvenience.
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
Which ones are foundational? That is, which ones must you master before you can learn the others? Start with those. Once you understand them, the rest you can pick up when you need them.
Will Rogers never met me.
-
- Bacon 1) Beer 2) Sunshine After that is up to you.
-
- Bacon 1) Beer 2) Sunshine After that is up to you.
- Elephanting Sunshines
-
I have a big question (at least nightmare for me). I got confuse between lot many technologies, like some times I wanted to learn about OS internals some time about web design sometimes about UML and other time about Design pattern. At times I also planned to work on Mobile development and cloud computing also. Can anyone suggest how should I prioritize the things.
Eventually you will have to learn all of them, at least to a certain depth. On which ones you will need more depth depends on where you are going to end up in the industry. So you can as well start with any of them, as long as you find it fun to work with them. When you like a subject and are well motivated your learning process will be a lot faster. So start with the things you like most and try find a job in which you can play these cards well. In the course of your life you will detect that you might like some of the other subjects as well and pick them up. New technologies will show up, and some of the existing ones will turn out to be no longer a factor. One general tip: No matter which area you will work in, good software design work is always a big advantage. That doesn't necessarily mean that you should learn UML first. It is more your the attitude towards software design than the tool you are working with. Good luck!
-
Eventually you will have to learn all of them, at least to a certain depth. On which ones you will need more depth depends on where you are going to end up in the industry. So you can as well start with any of them, as long as you find it fun to work with them. When you like a subject and are well motivated your learning process will be a lot faster. So start with the things you like most and try find a job in which you can play these cards well. In the course of your life you will detect that you might like some of the other subjects as well and pick them up. New technologies will show up, and some of the existing ones will turn out to be no longer a factor. One general tip: No matter which area you will work in, good software design work is always a big advantage. That doesn't necessarily mean that you should learn UML first. It is more your the attitude towards software design than the tool you are working with. Good luck!