3 ms·
>And as for the "layers" argument - if there are too many layers of dependencies to keep track of, something is very, very wrong with the technology you are usi
by Cederfjard 8y ago
>And as for the "layers" argument - if there are too many layers of dependencies to keep track of, something is very, very wrong with the technology you are using. (And yes, I do consider modern web tech completely insane.)
So you were basically being glib about the salaries, since you know a lot of us are in that position? What do you suggest we do?
When I list the dependency tree of our project at work I get ~5500 unique packages (many are different versions of the same ones). Does the fact that I don't know them by heart mean that I'm being paid too much?
- pferde 8y agoNo, if anything, I think anyone working in your field is not being paid enough for working with something as bonkers crazy. :) But seriously, I haven't said that you have to be able to recite the dependencies when woken up at night, just that you should have an existing internal methods of keeping track of them and auditing them, and not relying on some comes-one-day-disappears-the-next web service.
- JanisL 8y agoI think this is why a lot of people vendor dependencies and keep mirrors of anything particularly mission critical that they depend on. I've been involved in situations where this has been done for closed source code too via escrow services to make sure of continuity of product even if the other business closes for whatever reason.