738

average day in NPM land (programming.dev)

submitted 3 months ago by sus@programming.dev to c/programmer_humor@programming.dev

128 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] TootSweet@lemmy.world 205 points 3 months ago

I've literally told my coworkers "I'm not saying we should never use dependencies. But every time you add a dependency, you should hate yourself a little bit more. Some self flagellation can't hurt either."

[-] sukhmel@programming.dev 11 points 3 months ago

So, every time I use a library to recognize patterns on a picture, to interact with Kafka, do some SSL, or do database mapping, I should hate myself, noted

We did Elastic API integration in Java by creating and maintaining huge half-codegenerated transformer from code to Elasticsearch's JSONs, it was a pain and it was source of more than one error

Dependences should be reviewed and audited to make sure they do what you need and they are worth using. Just making everything in-house gets you nowhere most of the time

[-] aaro@lemmy.world 24 points 3 months ago

Nobody is arguing that you should never depend on anything and create everything yourself, but adding a dependency for literally a one liner function is awful. Like one of the Go proverbs goes, a little copying is better than a little dependency.