What do you do if you want to master a new programming language as a software engineer?

In my opinion, acquiring a new language shouldn't be a major concern. Instead, prioritizing problem-solving skills is crucial for success as a developer or programmer.

Software engineering is a tool, not an end in itself. First pick a goal, then learn the appropriate tool for the job. Most engineers are constantly learning new tools.

Learn something that matters. Learning some obscure isn’t that cool might seem like a good idea. If you’re going to take the time, invest wisely. Your time matters.

By starting a new project. This has been the best way to learn a new tech or anything really. It enables you to open up your mind to creativity and new ways of doing things. Try and error enhance the experience and knowledge allowing you to explore different approaches that others may have already took which saves a lot of time and leads to the right path of learning new things!

From Beginner to Professional in this journey I learned from Scratch to Expert, & still learning-growing so that's coming from my own experience:- To master a new programming language as a software engineer, start by understanding its fundamentals like syntax & data types. Then, dive into hands-on practice through coding exercises and projects. Utilize online resources like tutorials, documentation, and forums for guidance. Collaborate with peers and join coding communities to exchange knowledge and get feedback. Constantly challenge yourself with increasingly complex problems to reinforce your understanding. Finally, stay updated with the latest developments in the language to refine your skills continually. Hope it help's you, Thanks!

Just start coding, then you will feel better this language ;) Theory is good only if it can be applied in practice. Goal is clear when know what you can do with new language.

Set realistic goals. It might seem like a good idea to tear through five hours of videos. You need to retain the information. Set realistic goals and achieve them.

I find that the classic leetcode-type exercises make a really good tool for learning a language. Try to solve one problem in as many ways as possible given the chosen language. If you're learning Java try solving the same problem with for loops and streams for example.

Learning new language should be divided into multiple goals. - Lean the basics of langualge by solving common problems like P-99: Ninety-Nine Prolog Problems or leetcode - Put this language to use in project like small web app This not only helps to lean basics but also get familiar with community and eco-system.

Setting clear and succinct goals is one of the most crucial thing to do, and sadly, one of the points that most of us miss out on a lot. While having a North Star for any new language or skill is good to have, we should probably focus more on the smaller time-bound goals. For example : - Start with a "Hello World" code. - Try to start adding more complexities week on week, etc For me, the Basic principle here is "Enjoy the Journey, and you won't realize when you have reached the destination."

Simple steps but depends on requirement. A. Out of curiocity: 1. Learn basics from any course 2. Try some code on interactive platforms B. Need for work temporarily 1. Everything in A, 2. Understand project existing code 3. Learn to debug well 4. Learn to read code well C. Expertise 1. Everything in A and B 2. Still read famous author books 3. Learn best practices 4. Follow and read some blogs 5. Learn frameworks around it 6. Practice different scenarios

At the end of the day a complex project is a carefully arranged collection of fundamental constructs that work together to solve a problem.

Learning the foundation is critical for every endeavor. Of course you need to learn the basics. The foundation is the house to which you will always return.

Building the fundamentals is often the most important and the most neglected step. While, we are always in a crunch of time to take in a new language in its entirety, we should always remember that with a strong foundation we can withstand any challenges.

Learning fundamentals of any programing language is a core concept. Without learning the fundamentals it's difficult to move forward as you build your entire learning upon it. Do not be in a rush to develop something. Learn the fundamentals and create something which adhere fundamentals and which shows what you learned. You don't need to memorize everything. Instead always try to understand the concepts behind them. Apply them to real world examples; it might be way easy to remember them by doing so!

The only way one can learn something is to do it. When you do something a lot, you learn to improve. The expert in the field is most critical of the field. The expert knows the shortcomings and when to use the tools and, equally if not more importantly, when not.

Se dice que para ser experto en algo se necesitan 10.000 horas de estudio o practica. La unica forma de conseguirlas, es estudiando o practicando. Adelante...

Keep learning daily or in a set pace by yourself. Do not fall off after few days and start again in a month or so. Always try to set a goal and achieve it daily or as you see fit. Always keep in mind consistency is key. Participate in coding challenges, solve problems, create small pet projects to showcase what you learned!

To master a new programming language as a software engineer, practice coding daily. This consistent exposure reinforces syntax and patterns, deepens your understanding, and builds muscle memory. Tackle diverse challenges to cover various aspects of the language, from basic constructs to advanced features. This approach not only sharpens your skills but also boosts problem-solving abilities, making you adept at using the language effectively in different scenarios. Pair this with studying documentation and collaborating with others to gain different perspectives and insights.

Consistency is the key to any success, so find every day at least a small challenge to solve. It can be from a project development to a simple code challenge.

In my view you don't frequently start learning a language for the purpose of learning a language. You start learning a language for the purpose of solving a problem that this language is good at solving. This is a very successful way of solving a problem and learning the new stack at the same time.

Do it. Only way to learn something is to do it for real. When that code goes into production and the team has to live with the outcome, then the code is “real”!

I’ve generally found doing projects helpful in learning a new language or using advent of code problems or leet code problems. This approach has given me concrete examples of how the language can be used. Once I’m familiar with the syntax and style I can dive into the theory behind the language.

Similarly to learning a new speaking language, you can never master a programming language without using it to create a real project. .

Once you get the hang of the language you are trying to learn, start building simple projects. It doesn't have to be too complex. Gradually increase the complexity with time. Try to innovate new ideas into it. Try to solve real world problems/ apply real world scenarios into your application. You may run into ton of problems & that's great! They are the stuff you can't learn by just reading a book or watching a video. Troubleshoot them! Learn! Code! Repeat!

There are other people in the same situation as you, others with greater expertise and also some starting the road. Either you can learn from them, help them or share common stands. Never feel alone while learning!

Engaging in community is great way to lean about hard parts of the language. Those common problem which you are about to encounters, someone have already faced them and has a solution.

This is how I do it. Let’s say I want to learn MEAN: 1. Familiarize myself using articles or YouTube videos. 2. Do some coding exercises. For MEAN, it would be a basic CRUD application. If it's a new language for me, such as TypeScript, then I will try solving some problems on LeetCode using it. 3. Read a book on the topic. This is important for me, and I do it when I am ready to make a significant commitment to a tech stack. 4. Then, undertake a bigger project when opportunities arise. The time for steps 1-3 is now, so I am best prepared for step 4 in the future.

I highly recommend checking design patterns, from the basic set and how they can be implemented in the language, to some others that might be particular to it.

Think of how that language or technology fits in your mind map. How does it resemble things you otherwise knew, and what new concepts does it introduce to you? Put emphasis on the latter, do these concepts offer potential paradigm shifts in the way you see things? Here's from Alan Perlis (albeit lacking pragmatism, even languages that bring nothing new, enforce what is already there, to an extent) : "A language that doesn't affect the way you think about programming, is not worth knowing."