A language is a means to an end. Quickly picking up programming languages allows developers to build anything. I've recently been learning Java to contribute to a Spring backend.
I've found that once the foundations of the language have been learned, a great way of learning is to develop a process of cycling through learning details, then putting them into practice.
The first thing to do is understand the core concepts of the language and the main use cases. If you can, get an experienced engineer to mentor you. This way you'll cover the mundane setup stuff and be running code in no time. Spend about a day or two here, enough time to know everything to get you started but not too much that you end up bored and lose motivation.
Ask yourself the following questions:
- What tools do developers generally use and why?
- A good starting point is to ask what's the most appropriate text editor / IDE to use.
- Understand why developers use these tools and what others exist but they don't use. Remember that if all you have is a hammer, everything looks like a nail.
- What's the type system?
- What's the programming paradigm?
- Is it object-oriented, functional, etc?
- Is it limited to a specific paradigm or does it support numerous? It's common for a language to support multiple paradigms
- Is it compiled or interpreted?
Most of the above high-level questions don't have an absolute answer which is why exploring these questions and answers is key. This will allow you to establish strong foundations, on which to learn the details.
At this point you'll hopefully have some vague idea of what the language does and how to execute some code. So now it's time to get to grips with how to write it.
- Learn some syntax, for example:
- How are variables and functions declared?
- What are the available control flows? e.g. if statements, for loops
- What are the core data structures and how do you create them? (e.g. arrays and dictionaries)
- What kind of features does it have? For example:
- What's available in the language's standard library?
- What are the main conventions people follow?
Theory is great, but we learn much more through experience. Nobody learns how to ride a bike by reading a book about it. Try out one of the following in order to gain experience:
- Contribute to an existing project at your workplace, pair with another developer if you can.
- I've found that going into an established codebase where good practices are followed has been awesome. It'll be easier to add new small features by extending existing code or by following existing patterns.
- Code reviews by other developers will help point out issues quickly.
- Contribute to an existing open source project. It's common for projects to mark issues that outsiders can pick up, this is a great place to start.
- Create your own project. Find something you're keen on creating and build it with the language you're learning.
Lastly, stay out of your comfort zone and push yourself to constantly learn.
I’d like to thank Emily Woods for reviewing this article.