5 ms·
When I was a kid, we've been told to be cautious with third party dependencies, that code can do anything and it's a risk to evaluate. With the new generation
by SupLockDef 5mo ago
When I was a kid, we've been told to be cautious with third party dependencies, that code can do anything and it's a risk to evaluate.
With the new generation of yolo NPM scripters, they simply don't evaluate the risks. They will even fight back telling you that it's the way of doing things.
In reality, it's the warning we learnt back then, that's the result of be mindlessly importing third dependencies without thinking.
In other words, the risks were always there, the new "modern way", let's put it that way, doesn't put the effort anymore.
- andrekandre 5mo ago> that's the result of be mindlessly importing third dependencies without thinking tbf, most tech-related corporate environments don't want you to think, just do (kpi, mbo, okr et al) and this is one of the results
- zelphirkalt 5mo agoThat, and it is combined with not being willing to write a few functions oneself, which one could easily do, and then not have to add a dependency. But it is also a result of trying to do everything quickly quickly! and being pushed to do that. The more one knows about computer programming, algorithms, data structures, how things are usually implemented in general, the better one can avoid unnecessary dependencies. Needs the right environment though to execute on that.
- BigTTYGothGF 5mo ago> When I was a kid ... With the new generation Let's be real tho, there's a whole lot of people who have been around enough to know better that do this too.