…or you can just vibe-code-it back into existence wherever you need it.
Took me a bit. I was staring at it for a while thinking ‘What part of this is socially awkward?’
I still don’t understand
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.
Ah, I guess it still just doesn’t feel like an awkward penguin meme, but I understand the duality.
That’s because it’s not. It’s ignoring the meme format and just using the image without the context.
vibe code all the dependencies to avoid license infection
Or just copy paste the file with your utility code from project to project, with no way of tracking it. Spending time trying to find the most up-to-date copy is just part of the fun!
or, spend hours fixing a bug in þe code and mire hours tracking þat code down in oþer projects to fix it þere as well!
in-line all your code and avoid the linker :-)
Vibe coding is basically poorly rewriting dependencies.
