I think why most people make emphasis on learning language before framework is because it is very easy to get carried away with what the framework offer without making attempt to revisit how things actually work under the hood.
Understanding how things work under the hood help during scalability and application performance.
But in all, no perfect system, we are only trying our best.
I'm a software developer who writes about Laravel, JavaScript, Rails, Linux, Docker, WordPress and the tech industry. Follow me on Twitter @tylerlwsmith
I understand that knowing how things work under the hood can be valuable, but the further I get into my career, the less important the implementation details of any given language or framework seem to be.
I write a lot of PHP and JavaScript, but occasionally I need to work on existing Django or Rails projects. I don't write Python or Ruby often, but when these projects come up I need to create a feature or fix a bug quickly. Though I'm not great with those languages, I find that a solid grasp of software architecture and clean code can get me through the features most of the time. Writing good code is the hard part: I can look up the syntax and individual commands as needed.
For engineers that have written code in dozens of languages, many of them seem to learn languages and frameworks at the same time for a project. They have experience with several paradigms and tools, so they are able to figure it out as they go.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think why most people make emphasis on learning language before framework is because it is very easy to get carried away with what the framework offer without making attempt to revisit how things actually work under the hood.
Understanding how things work under the hood help during scalability and application performance.
But in all, no perfect system, we are only trying our best.
Thanks for reading my article, Hammed.
I understand that knowing how things work under the hood can be valuable, but the further I get into my career, the less important the implementation details of any given language or framework seem to be.
I write a lot of PHP and JavaScript, but occasionally I need to work on existing Django or Rails projects. I don't write Python or Ruby often, but when these projects come up I need to create a feature or fix a bug quickly. Though I'm not great with those languages, I find that a solid grasp of software architecture and clean code can get me through the features most of the time. Writing good code is the hard part: I can look up the syntax and individual commands as needed.
For engineers that have written code in dozens of languages, many of them seem to learn languages and frameworks at the same time for a project. They have experience with several paradigms and tools, so they are able to figure it out as they go.