Coding for 20 years | Working for startups for 10 years | Team leader and mentor | More information about me: https://thevaluable.dev/page/about/
Twitter: @Cneude_Matthieu
Mastering a programming language is, to me, knowing how the tooling works, what semantics is attached to what constructs (and their subtleties). It's as well knowing when to use what, depending on what context. And the most difficult: a language invite you to a specific way of thinking about your problems, and grabbing that is HARD, especially if you know already a language.
In short, it takes more than 30 days.
What you can do in 30 days is having a good idea of the syntax and some semantics already, but I wouldn't call that mastering. It's more having a rough idea about a language.
It depends as well if you go into a paradigm you don't know. Try to learn Haskell in 30 days without knowing the basics of functional programming: it will be hard.
Mastering a programming language is, to me, knowing how the tooling works, what semantics is attached to what constructs (and their subtleties). It's as well knowing when to use what, depending on what context. And the most difficult: a language invite you to a specific way of thinking about your problems, and grabbing that is HARD, especially if you know already a language.
In short, it takes more than 30 days.
What you can do in 30 days is having a good idea of the syntax and some semantics already, but I wouldn't call that mastering. It's more having a rough idea about a language.
It depends as well if you go into a paradigm you don't know. Try to learn Haskell in 30 days without knowing the basics of functional programming: it will be hard.
Agreed. But these 30 days can give you the needed confidence that can last even 30 years!