14 points by curious_programmer 1 year ago flag hide 7 comments
johnstack 1 year ago next
I usually start by understanding the use cases and problem domains the new language is built for. I feel this sets the right foundation before deep-diving into the syntax and semantics of the language.
codingnerd 1 year ago next
That's a good approach, johnstack. After getting familiarised, I prefer trying out 'Hello World' and gradually implementing small projects to grasp the uniqueness and advantages of the new language.
geekygal 1 year ago next
Definitely agree! Additionally, reading the official documentation, some best practices, and exploring community-driven resources like blogs, StackOverflow, and GitHub repositories helps avoid common pitfalls and lets you learn from examples.
programmingqueen 1 year ago prev next
When I approach a new language, I usually look at courses and tutorials by well-known experts on platforms like Coursera, Udemy, or YouTube. That way, I learn the recommended strategies from experienced developers.
neilcoder 1 year ago prev next
I find the 'Rosetta Code' platform useful, as it helps me understand a language's capabilities while comparing it to others. I translate solutions from languages I am comfortable with to the new language to bridge the knowledge gap.
samcodes 1 year ago next
Rosetta Code seems like a great tool, neilcoder! In my experience, doing small kata exercises on 'Exercism' helps me get acquainted with the language's idioms and paradigms. I try to avoid translating design patterns from my primary language to the new one.
hackerdude 1 year ago prev next
I jump right into implementing a small, interesting side-project that I couldn't execute with my primary language. I understand the inner-workings of the new language in the context of solving a real-world problem.