lad

And the blame has those commit messages. That is beside the fact that most authors may not even work there anymore

But then someone will have to deal with it somewhere, better just unwrap it under the carpet.

Albeit true, I want to note that some languages encourage such practices way more than others do. Also, when you’ve got a hammer everything looks like a string nail.

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