It's pointing out the conflict between two coding ideals - first, reducing duplicate code so that you don't have to reinvent the wheel and/or copy-paste code (which often means making calls to libraries) which is represented by the red penguin facing right, and second, wanting to reduce dependencies so that external variables are reduced (which would mean including code in your codebase that otherwise would be an external library call) which is represented by the blue penguin facing left.

The closer you get towards one ideal, the further away you get from the other.

For sure. But I've seen a lot more sins committed in the name of reusing code than in the name of minimizing dependencies.

Plus, it's bloat. A snippet of extra code isn't going to cause much trouble, but then you end up doing it a lot, and there's snippets in the snippets, and all the sudden something that used to fit on a floppy is 3 gigs.

I have no idea how much of a factor this is relative other various performance-sacrificing shortcuts, but Wirth's law is a thing.

I also think an implementation should depend on how many the developer remembers to change