[salawat]

I want to point something out from an information tgeoretic point of view.

Can you say you know what is going on if you don't read the implementation code? I'm even fine with extending that to executable code.

You must read code. Code use sans understanding is dangerous. You can do immense harm without even realizing you're doing it. Look at Log4Shell, or MCAS.

The majority of your time as a computing professional should be spent reading code you'll be using. Abstraction is nice. Until it isn't.

I'll never understand the I shouldn't have to read code school of thinking. It's like saying you should never have to learn arithmetic.

Now there's a case to be made that in development communities that value convention, yes, you can get to a point you don't have to read as much code in that community, given everyone plays by the rules.

Colors.js or node-ipc is what happens when they don't. So even then, don't read at your own peril.