loading...

re: Why You Shouldn't Use A Web Framework VIEW POST

FULL DISCUSSION
 

I completely agree, i have seen bunch of people in various projects what they thought were front-end/full-stack devs. First thing they installed bootstrap and jQuery and spend hours of stackoveflow-ing how to use it, ended up in CSS/JS/HTML in the same 1 file, not scalable, testable nor maintenable application/web. Having tens of ($)plugins what are doing the same thing, but why not use every time different one? It's so easy and convenient, but having no idea about synchronous javascript and calling yourself a developer is out of common sense.

When i introduced CSS/SASS/Vanilla JS they were completely lost, they couldn't understand any of the OOP or Classes nor "this". Idea of having JS/CSS/HTML in separate files was completely new to them. Funny the same developers were pushing to use React or Angular - very scary scenario.

Having a deadlines or doing your job is not an excuse for anybody's knowledge! I would not trust doctor, surgeon, painter, construction worker... if they would have no idea what they are doing but they can somehow deliver because it's their job.

If you want to learn and be a developer don't expect your company to pay you to learn - as it was mentioned you are there to give them solutions. If you want to learn about development take your own time for it, read, watch curses - whatever is the best for you, just don't expect that somebody will tell you at work to take time off to learn how to write code.

I have taken an approach in our team to completely strip and get rid of anything jQuery and re-wrote it in Vanilla JS. Now i can really see what is the maturity of our team and once we get the basics right we can think of a framework what will embrace our work and our effectiveness.

 

It looks like the real issue is the learning material or the will to learn by devs, not the existance of frameworks on some internet page 😛

 

This guy gets it.

The entire discussion here is a red herring: "the noobs use frameworks as a crutch because they can't code good, therefore frameworks be bad"

We should focus on teaching juniors good programming principles instead of trying to convince everyone that frameworks are a bad idea.

 

If I had no budgetary constraints in most jobs I held, I would code in assembly

code of conduct - report abuse