3 ms·

I'm talking about how that's completely not feasible anymore because of how every project has dependencies upon dependencies upon dependencies because the gener

by mdszy 7y ago

I'm talking about how that's completely not feasible anymore because of how every project has dependencies upon dependencies upon dependencies because the general development attitude has shifted towards "import a single library that tells you if a number is odd, and another library to tell you if one is even"

mperdoni 7y ago
Ultimately, if a bug in a library causes issue with your program, and your company loses $X, your superiors will not give a shit. You have the burden of responsibility for the program. For common major libraries used worldwide in enterprise products, you are right in that there is an element of trust. They are made by people much faster/better/stronger than most of us. If all else fails, the sheer magnitude of people using it is a small insurance policy, as disastrous issues will probably be quickly apparent. That still doesn't absolve you of responsibility, but the overall risk is usually pretty low. A segment of code on SO, or a weeny niche library? You only have your noggin to vouch for its stability and accuracy.
- mdszy 7y ago
  >They are made by people much faster/better/stronger than most of us. lmfao no they're not
- jodrellblank 7y ago
  > You have the burden of responsibility for the program. What does that mean when the developer who committed it might have left long ago? I'm assuming you mean more than "blame" which is a pretty unhelpful response for a company to have, but then what exactly is "burden of responsibility" which should have this bus-factor-of-1 attitude around it, and why?