Times have changed. We moved from making fire with sticks to amazing things like 3d printing, biotechnology, block-chain and artificial intelligence. No doubt- we are only starting. But one thing is of worry- how we learn. Learning can be subdivided into 4 parts(in the particular order) namely:
These can be applied to the Technology, Business and Finance and the Leadership and Management branches. The main goal nowadays is not to be an expert if you want to quickly build your career and make some money in the process. The main aim for now is to gain competence. Why I say that is because it is cheaper for an organisation to get someone with competence as opposed to getting an expert. The most efficient way is to aim for the skill level as opposed to the expert level(which tends to come by itself as you sharpen the skills level) We want to maximize financial benefit from the most efficient way possible.
1. Fundamentals
Fundamentals encompass the basics such as syntax and methodology. So in the learning age for developer you need to note the following items:
2. Information
Where does one get curation - University guides, Certified professional guides and lastly at least two books on the subject.
Where does one get knowledge - books are best for fundamentals but they quickly become obsolete (we both agree that technology is a fast evolving animal). Online courses are good but they are a poor source of curation. Documentation is also a good source. (Although they have possibility of lagging behind especially in open source projects - as developers tend to focus more on the code as opposed to the documentation) Schools and classes are also good (even though they tend to be very expensive)
3. Skills
Knowledge invariantly leads to skills if you add practice. Find problems to solve on your own from sites such as stackoverflow, stackexchange and github. Before you look at the answers - try solve the problem on your own. This gives you the practice and hands on experience.
Where does one get the support and discipline needed?- The strength of schools in adding to this is that you write exams but you can work with others and get informal training at work.
4. Expertise
The same sources and skills. Skills lead to expertise. An interesting thing to note is that if you do answer a question that has no answer currently on a forum - you are already an expert when it comes to that question.
Where does one get certification - College body and Company certifications can be very good sources
Remember - skills bring the money and if you look up books over a year old - try new for newer versions and go through the sample tests and mock exams to get a feel of what you will be getting yourself into. We live in an era with abundant sources of knowledge and information - I hope this article will help you as you journey through the world of software development.
Credits :
Dan Appleman's channel on Pluralsight.
- Fundamentals
- Information
- Skills
- Innovation
These can be applied to the Technology, Business and Finance and the Leadership and Management branches. The main goal nowadays is not to be an expert if you want to quickly build your career and make some money in the process. The main aim for now is to gain competence. Why I say that is because it is cheaper for an organisation to get someone with competence as opposed to getting an expert. The most efficient way is to aim for the skill level as opposed to the expert level(which tends to come by itself as you sharpen the skills level) We want to maximize financial benefit from the most efficient way possible.
1. Fundamentals
Fundamentals encompass the basics such as syntax and methodology. So in the learning age for developer you need to note the following items:
- Platform - platform chosen is very very important. In fact, platform can be a bigger issue in comparison to the programming language.
- Architectures
The drunken sailor problem is a classic example problem in computer science typically used to demonstrate the monte carlo method - solving a problem through simulation
2. Information
Where does one get curation - University guides, Certified professional guides and lastly at least two books on the subject.
Where does one get knowledge - books are best for fundamentals but they quickly become obsolete (we both agree that technology is a fast evolving animal). Online courses are good but they are a poor source of curation. Documentation is also a good source. (Although they have possibility of lagging behind especially in open source projects - as developers tend to focus more on the code as opposed to the documentation) Schools and classes are also good (even though they tend to be very expensive)
3. Skills
Knowledge invariantly leads to skills if you add practice. Find problems to solve on your own from sites such as stackoverflow, stackexchange and github. Before you look at the answers - try solve the problem on your own. This gives you the practice and hands on experience.
Where does one get the support and discipline needed?- The strength of schools in adding to this is that you write exams but you can work with others and get informal training at work.
4. Expertise
The same sources and skills. Skills lead to expertise. An interesting thing to note is that if you do answer a question that has no answer currently on a forum - you are already an expert when it comes to that question.
Where does one get certification - College body and Company certifications can be very good sources
Remember - skills bring the money and if you look up books over a year old - try new for newer versions and go through the sample tests and mock exams to get a feel of what you will be getting yourself into. We live in an era with abundant sources of knowledge and information - I hope this article will help you as you journey through the world of software development.
Credits :
Dan Appleman's channel on Pluralsight.
Comments
Post a Comment