What to learn and what to skip

Question

5.00/5 (1 vote)

See more:

Hi All,

I am C++(Unmanaged)/.Net developer. 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.

Happy Programming

Posted 1-Mar-12 6:24am

sumitskothari

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-03-01T06:31:00

This is too difficult question to give a comprehensive answer. You need to learn how to prioritize by yourself. Generally, you need to focus on fundamental aspects and fundamental knowledge and try to skip on application technologies and particular products, libraries, APIs, etc., but only if you are not using it in your immediate work. The fundamental knowledge should be as deep as possible. You need to strongly concentrate on depth rather than on width. Again, very hard to teach this skill. It comes with experience. Or not.

—SA