In theory I agree. But learning something just well enough to get your foot in the door as a junior will have immediate rewards and then you can learn more deeply.
Absolutely, I agree. But don't get lazy then and really take the time to learn the basics. Aside from all the webdev focused MOOCs and courses on the internet there is plenty of stuff about Computer Science theory and whatnot available, so the opportunity is there.
> But don't get lazy then and really take the time to learn the basics.
Here was a typical (not verbatim) exchange when I was a Front-End Architect interviewing candidates for my team back in 2012 or so:
---
Q: Tell me about your experience with JavaScript.
A: I know JavaScript because I've been working in jQuery for a year.
---
Further questions would isolate the fact that they've _only_ used jQuery. It was depressing, really.
I mentor developers to really strive to learn and understand the fundamentals precisely to stop propagating the idea that libraries and frameworks > fundamentals. Problem is, I've already started to witness history repeating itself when interviewing candidates and getting the equivalent answer above--but with "React" in its place.
I’m your prototypical computer geek - started programming in the mid 80s in middle school in Basic and assembly language, got a CS degree, bit twiddled in C and C++ for over a decade, but my experience over the last decade, makes me doubt the need of most developers to need to focus on computer science.
Most developers will never need to solve “hard problems”. They will be working on yet another software as a service CRUD app or a bespoke line of business app that will never see the light of day outside of their organization.
I’ve found studying architecture, soft skills, and my business courses (before I dropped out of graduate school) to be much more helpful in my career.