Introduction : Learning as a software developer
What to learn and when you should learn it is the hardest problem to solve as a software developer. There are tons of things you could potentially learn, with sites like Reddit and Hacker News adding new must-learn skills and technologies to your pile every week. How do you ignore the noise and choose the best skills to learn without being overwhelmed? In which skills you should invest your limited time and energy to get the best returns?
To give you a clear idea of how to grow your skills as a software developer and how to learn those new skills, I wrote the following series:
- Mastering your mindset and learning for the right reason is the first part to understanding how to learn the right way. In Learning: FOMO, need to relevant or drive to grow?, you’ll learn more about what is pushing you to learn.
- Knowing where you are and what are the skills you can use right now will help you understand what you should learn next. In Taking control of your learning by mapping out your skills, you’ll start taking control of your learning by mapping out your current knowledge.
- Once you know where you are, you can choose what are the most valuable skills you could learn. In What is the next skill you should learn as a software developer?, you’ll learn how to choose your next skill to learn according to your goals and interests.
- Finally, when you’ll have chosen the next skill to learn, you’ll need a process to learn it quickly and efficiently. In My 3 steps process to learn new skills as a software developer, you’ll learn my favorite process to break down new skills in smaller part that are easy to understand.
If you want to read even more about learning and growing, stay up to date and do your best work as a software developer, sign up to my newsletter below to get posts such as these delivered straight to your inbox.