I'm not sure it's that important to learn all those frameworks/languages as you never really become a master at anything why not pick one and do it well?
No. It is not. It's just to give beginners of an idea of which framework they should choose. Like, if someone knows PHP, then it will be good to get proficient in Laravel as it's more in-demand these days.
Learning all is not necessary but a mid-level dev should at least know them. For beginners mastery of one language should be the goal. Afterwards, they can move to others.
You never really master anything in the world of programming and to say you have mastered anything is arrogant. I think you've done well with the title of the post it's very click baity. I just hope new junior developers don't think they have to learn them all as you don't and knowing one well will serve you well throughout your whole career
Mastery means one should be good on that language or framework. Everyone knows that you cannot master anything being a human being. I never advised new devs to learn all of them. I re-iterate that one language should be focused. I disagree that knowing one will suffice through whole career. If you work on some fast paced environment technologies also change rapidly and you accordingly as a dev have to evolve with that.
While I do appreciate the benevolent intention of introducing new devs to these frameworks, the title definitely sounds like you're suggesting one to complete all five tutorials. To add value to this article, I would suggest leaving out the descriptions of all the frameworks since they all sound the same, and talk about why you're recommending these tutorials - which should be the focus of this article.
Yup I agree to that. As a developer you are correct, but if you think as a writer, titles have to be a bit of attractive. So, that's why I have made the title like that. Yup. Soon, I would be listing all frameworks, listing their advantages and disadvantages so that the decision is more easier for juniors to pick up the framework of their choice. Thanks for you input BTW.
Because there is not a single one-size-for-all framework that deals with every situation possible in the most optimized manner. It is always good to explore different languages, frameworks and ecosystems to compare pros and cons.
Though, it is probably a good idea to focus one first so that you know what to compare with others.
I'm not sure it's that important to learn all those frameworks/languages as you never really become a master at anything why not pick one and do it well?
No. It is not. It's just to give beginners of an idea of which framework they should choose. Like, if someone knows PHP, then it will be good to get proficient in Laravel as it's more in-demand these days.
Each solves the same problems in slightly different ways you learn more by trying out a few of them at least.
Some patterns are explained more clearly in the documentation of one or another framework and their popular libraries.
Sure master one of them, but it doesn't hurt to try out alternatives every now and then.
Yeah master one of them and then also taste others. You never know whenever that one becomes trendy.
this!
Learning all is not necessary but a mid-level dev should at least know them. For beginners mastery of one language should be the goal. Afterwards, they can move to others.
You never really master anything in the world of programming and to say you have mastered anything is arrogant. I think you've done well with the title of the post it's very click baity. I just hope new junior developers don't think they have to learn them all as you don't and knowing one well will serve you well throughout your whole career
Mastery means one should be good on that language or framework. Everyone knows that you cannot master anything being a human being. I never advised new devs to learn all of them. I re-iterate that one language should be focused. I disagree that knowing one will suffice through whole career. If you work on some fast paced environment technologies also change rapidly and you accordingly as a dev have to evolve with that.
While I do appreciate the benevolent intention of introducing new devs to these frameworks, the title definitely sounds like you're suggesting one to complete all five tutorials. To add value to this article, I would suggest leaving out the descriptions of all the frameworks since they all sound the same, and talk about why you're recommending these tutorials - which should be the focus of this article.
Yup I agree to that. As a developer you are correct, but if you think as a writer, titles have to be a bit of attractive. So, that's why I have made the title like that. Yup. Soon, I would be listing all frameworks, listing their advantages and disadvantages so that the decision is more easier for juniors to pick up the framework of their choice. Thanks for you input BTW.
Because there is not a single one-size-for-all framework that deals with every situation possible in the most optimized manner. It is always good to explore different languages, frameworks and ecosystems to compare pros and cons.
Though, it is probably a good idea to focus one first so that you know what to compare with others.
Exactly Edward. I suggest the same. Thanks for your input.