3 ms·
> the sheer amount of stack knowledge and framework knowledge required to do anything as a webdev these days I think this is greatly exaggerated. You can get b
by jimmaswell 8y ago
> the sheer amount of stack knowledge and framework knowledge required to do anything as a webdev these days
I think this is greatly exaggerated. You can get by just fine making your own sites knowing some basic html/css/maybe js, maybe some php too if you want backend stuff. Optionally some frameworks if you want, which should usually be easy enough to just follow some examples and get the functionality you want pretty fast.
If you're put on an existing web project, you probably only have to learn the bits immediately surrounding the things you do, picking it up as you go along. I still don't know Angular, React, Vue, or much else in the way of JS frameworks other than jQuery after being in web dev professionally for years, as it simply hasn't been needed.
- llamataboot 8y agoYeah, sorry if I wasn't clear, but that's kind-of my point. You can make a site by knowing how to use some subset of stuff, but the rest you use as a black box - whether it is importing a bunch of third party libraries or being able to build a web app without understanding how cross-site attacks work, etc etc so at some point you either have to learn these little gotchyas all over the place or they go un-fixed. Like how many sites still don't have mandatory HTTPS even though it is free and easy?
- jimmaswell 8y agoThat's no different from programming in any other environment then - good libraries are generally meant to work like black boxes and security issues etc happen everywhere.