I agree with this article and also appreciate the points made in the comments.
When I first started out in my career I used frameworks heavily. I knew there was a lot under the hood that I didnt understand yet. When I became comfortable enough with a variety of frameworks I took a step back and decided to learn how everything actually works. Was kind of a big eye opener for me.
I appreciate how frameworks can make things quick and easy to develop a project, but I personally like to look at what a framework has done well and use the individual components I actually need and create my own libraries. I dont like relying on things that might fade from existence sooner than later and prefer to use the language these frameworks are based on.
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 agree with this article and also appreciate the points made in the comments.
When I first started out in my career I used frameworks heavily. I knew there was a lot under the hood that I didnt understand yet. When I became comfortable enough with a variety of frameworks I took a step back and decided to learn how everything actually works. Was kind of a big eye opener for me.
I appreciate how frameworks can make things quick and easy to develop a project, but I personally like to look at what a framework has done well and use the individual components I actually need and create my own libraries. I dont like relying on things that might fade from existence sooner than later and prefer to use the language these frameworks are based on.