Learn Technologies Just in Need, Not Just in Time!
Learn Technologies Just in Need, Not Just in Time!
Looking for some advice to better your programming? Try these ideas, like learning technologies when needed, focusing on core concepts, and picking technologies worth learning.
Join the DZone community and get the full member experience.Join For Free
Whatever new awaits you, begin it here. In an entirely reimagined Jira.
Technologies come and go, and if you try to cope with new technologies you will almost fail, instead you will feel disappointed!
Even if you try to follow a single technology, like .NET, for example, you will not be able to make use of all its advancements!
On the other hand, if you buy in every new trend and try it directly in your production code, then be prepared for disasters! One of the popular reasons of software project failures is depending on immature technologies!
I have heard some geeks said that they didn’t use any product of Microsoft till the first service pack is live!
Even if we take their words seriously, we will not be able to apply this advice to all new technologies. And it seems that the solution may be to avoid learning new technologies altogether!
But how to keep competitive in this dynamic industry?
1- Spend Most Your Time Learning Core Concepts.
When I interview a candidate, most of the questions I used to ask related to technology agnostic concepts. Concepts that will not fade with time and differentiate geeks from amateurs.
For example, I rarely ask a candidate if she knows OOP concepts or what she knows about design patterns, instead, I give her a simple problem that could be simply solved by applying a certain pattern.
Among the concepts that I believe any serious developer should invest most of his time in:
- Object Oriented Programming (OOP)
- Object Oriented Design (OOD)
- Design Patterns
- Database design
- Algorithms and data structures
- Mastering a general purpose programming language
2- Learn Technologies Just in Need, Not Just in Time!
Someone gave this advice before, and it helped me too much during my career path!
In brief, you don’t need to learn every new technology, and you can’t! But when you need a solution for a certain problem, then it’s time to learn a technology that solves this problem, or do it yourself!
But how do you know there is an existing technology that solves your problem?
3- Keep Updated With Emerging Technologies
Don’t learn new technologies till you need them, but keep monitoring the trends and know what problems are solved by which technology. I will tell you how I do this right now…
- Register in an RSS feeds aggregator, I am using Feedly
- Subscribe in important development sites’ RSS feeds. I am following a bunch of sites/blogs, but here are the most useful IMHO:
- DZone.com (Don’t miss their cheat sheets, or what they call RefCards)
- InfoQ.com (Don’t miss their Mini-books)
- I created an account on Quora some days ago, I can’t remember why! But they magically send very interesting content to my email, and it seems they have a strong recommendation system that they customize the content they send me day after day! So, go and create an account on Quora, follow some topics there, upvote some answers you feel good, and you will be impressed by the content they will send you, I promise :)
4- Select Technologies That Worth Knowing About, Not Learning
Actually, I rarely read a complete article from my feeds! but I keep passing through the titles, and I do this many times, every day! When I notice some technologies gain traction, that is, I see their names repeated frequently, I know this in the correct time to know what this technology is all about. I don’t learn how to use this technology, rather, I learn what problems it solves and may read some reviews from developers who already use it.
This advice has a good side effect. Many times you will be asked in technical interviews about technologies you don’t know. Good answers here is to provide an alternative. For example, if you are asked about NHibernate, which you never used, you can answer simply that you know Entity Framework instead! This gives the impression that you know what you are talking about, … and it works!
5- Select Technologies That Are Worth Learning
This advice is not for you unless you feel confident about your level of the first advice.
When you follow the previous advice (#4), you may find that certain technology gains more traction that it got adopted by giants, many companies has vacancies for it, ..etc. Then it’s time to start learning it. For example, Microsoft created TypeScript. People kept talking about it for a while. I applied the previous advice on it till Google announced that the next AngularJS version will be built using TypeScript. Now, it’s obvious that this is the correct time to adopt TypeScript (I didn’t make the decision to learn TypeScript till now, just for priorities)
This is the best advice I can give for the busy developer to keep competitive in the market.
If you feel it useful, kindly help to spread the word with your friends.
This post published first on my blog.
Opinions expressed by DZone contributors are their own.