One can argue that modules are good, but them depending blindly on newer versions like that was bad dependency management. I say this because I strongly believ

One can argue that modules are good, but them depending blindly on newer versions like that was bad dependency management. I say this because I strongly believe that reinventing the wheel is unnecessary and can bring more problems than not. There are many examples, and I could come up with a made up one, but here's a very real bug that I debugged from another programmer not so long ago: So, he came up with a JNI for SPSS's C library, applied it correctly, and got haunted for lots of months with an unsolvable bug. The problem? he miswrote the final copy of the file, and sometimes, some bytes where copied twice. He tried to solve this problem for a long time (and eventually lived with it because SPSS was still resilient to this) Is this concrete example of a 'module' ridiculously short? yes, but my logic still holds IMO.