Many times the "right" thing is a balance between using a library/module as a black box and implementing something yourself. It usually involves a lot of consid

Many times the "right" thing is a balance between using a library/module as a black box and implementing something yourself. It usually involves a lot of considerations. * License is it compatible with the rest of your code? * Relative size of module vs what you need from it. The size of the module introduces a non-trivial maintenance burden. * Difficulty of just doing it yourself. Is the thing you need to do non-trival? like say encryption? or Distributed Consensus? * Is the module compatible with the internals of your system? Will it require significant changes to how your code or application works? * Platform support? Will the module work on all the platforms your code/application will run on? All of these things influence the decision. A knee jerk response of "Just use X" may be right but you'll find yourself in the position of not knowing why it's right and thus unable to adjust if it ever stops being right.