Reinventing the wheel is often very beneficial - especially for new developers. You will learn a lot about wheels, and might even gain insights on how to make better wheels.
I don't actively avoid things, but often the best way to play with new ideas is just with plain JS. As an idea or project grows you will get a feel for whether using external libraries or frameworks would be beneficial.
True, but beginners should build things themselves first WITHOUT frameworks - gaining understanding about the basics of web development. Using a framework from the start will get you quick and easy results, sure, but you will have no real understanding about how anything works. This is 100% necessary if you intend to be a developer.
I've seen so many 'developers' who have just gone down the route of following tutorials, installing and configuring frameworks & libraries. They can get a site up and running, but once a serious problem occurs, or a change outside the scope of their very limited skill/understanding is asked for by a client, they are totally lost. The next stage for many of these developers is googling for an answer, then copying and pasting 'solutions' from StackExchange that they have no clue about how they work.
This is a terrible way to go about learning how to be a developer. Start with the basics, and build from there. Frameworks are a convenience to be used to prevent you having to do the basic stuff again and again - after you already understand that basic stuff
I completely agree with you. The sad part is that with most frameworks even the intermediate level coders end up using Stack Overflow or Github Issues as a reference with cases they've not encountered before. It's just javascript.
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.
IMHO absolute beginners should not start out by using frameworks
And if you're expert enough, you can make things without using frameworks.
Depending on the use case, that would mean to "reinvent the wheel", which is often recommend to avoid.
I'm a beginner and I don't know any framework as of now. I'm currently learning backend, then I want to build projects without frameworks.
But in the future I would most likely learn one. I think we can get a feeling when we should do that.
So are you avoiding frameworks and you're not considering them for a project in your toolbox even if they'd be a good fit?
Reinventing the wheel is often very beneficial - especially for new developers. You will learn a lot about wheels, and might even gain insights on how to make better wheels.
I don't actively avoid things, but often the best way to play with new ideas is just with plain JS. As an idea or project grows you will get a feel for whether using external libraries or frameworks would be beneficial.
True, but beginners should build things themselves first WITHOUT frameworks - gaining understanding about the basics of web development. Using a framework from the start will get you quick and easy results, sure, but you will have no real understanding about how anything works. This is 100% necessary if you intend to be a developer.
I've seen so many 'developers' who have just gone down the route of following tutorials, installing and configuring frameworks & libraries. They can get a site up and running, but once a serious problem occurs, or a change outside the scope of their very limited skill/understanding is asked for by a client, they are totally lost. The next stage for many of these developers is googling for an answer, then copying and pasting 'solutions' from StackExchange that they have no clue about how they work.
This is a terrible way to go about learning how to be a developer. Start with the basics, and build from there. Frameworks are a convenience to be used to prevent you having to do the basic stuff again and again - after you already understand that basic stuff
I completely agree with you. The sad part is that with most frameworks even the intermediate level coders end up using Stack Overflow or Github Issues as a reference with cases they've not encountered before. It's just javascript.