Insurance against LeftPad level events
When it comes to dependencies, there are two extremes in software development. Complete ownership of everything right down to the abstract data types e.g. "Yes I write my own open addressing hash table and hash map"; or on the other hand grabbing strangers' code left, right and centre e.g. "I'd rather have a dependency on some random, 12 line implementation of LeftPad because that's one less thing to bugfix, debug and maintain". As with all computer science trade offs, the majority feel comfortable somewhere in the middle. Done properly, I see the elegance of relying on small, composable dependencies but...
