DEV Community

Discussion on: Why You Shouldn't Use A Web Framework

Collapse
 
fabioemsm profile image
Fábio Moreira

Thanks for validating my opinion on this topic!
Somehow, that's not how it seems to work in business world, and I am speaking in a role of job applicant.
Companies seem focused in the number of frameworks one "know" instead of the quality of software one can build.
I've been having some trouble finding good enough jobs because I don't know as many frameworks as companies require me to. On the other hand, I know the languages behind those frameworks, way above average.
And if needed, I don't think that a framework is that hard to understand. Actually it is quite easy after you know the basics, but employers don't seem to get it.

Of course I know a few frameworks that I used to work with, but it can also be a problem because frameworks can sometimes enforce us to write bad code, poorly designed and hard to maintain.

Recently I started to feel the Imposter Syndrome, even though I was the best in all programming classes in college and, I can solve problems that some of my coleagues can't even grasp.

It surely feels reassuring when I hear someone say that the language is the most important and only then the framework.
I must not be completely wrong.