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

FULL DISCUSSION
 

I really wanted to react (pun intended) to this because it's a very interesting debate... but I'll be honest: there are already a lot of comments and "reading" most of them got me a headache so I'll keep it short:

A good dev should be able to do both.

But anyway, this kind of debate, while "fun", is irrelevant, because one little thing: reality. You make it sound like being a "<whatever framework> developer" is bad or insufficient, but hey, what are most companies looking for? Yup. People with actual experience with <whatever framework>, not "Captain Vanilla Web". And since the time and energy a dev can invest into learning things is limited, learning something that might seem irrelevant when searching for a job is not a viable option for everyone.

I'm not saying you are wrong or even that I disagree (truth be told, I would have been a 100% with you a few years back). Learning the basics is certainly useful and will make any developer "better", but still, given that it's not always an option, being a "framework developer" is actually a good idea too. And frameworks can actually learn useful things to young developers, but I've seen that point covered in others comments so I'll keep my 2 cents about that.

 

there are already a lot of comments and "reading" most of them got me a headache

Guess how I feel! 😂

but hey, what are most companies looking for? Yup. People with actual experience with , not "Captain Vanilla Web".

Captain Vanilla Web sounds like a fun comic.

I think recruitment is another mess that needs sorting out, and is probably related. These days I'd just lie on a resume in order to get to the interview stage (where they ask you to invert a binary tree on a whiteboard, then hire you to do something completely unrelated to all of the above).

code of conduct - report abuse