HOW

FUCKING

HARD

IS

IT

TO

DOCUMENT

HOW

YOUR

LIBRARY

WORKS

ONE

EXAMPLE

FOR

A

FUCKING

POSTGRES

CLIENT

LIBRARY

IS

NOT

SUFFICIENT

Especially java clowns, most of the time they don't even bother creating a readme or single sentence that describes the project

Java clowns not using javadoc because it's Java boilerplate and requires a lot of effort to do that right.

@NeatNerdPrime Javadoc and other source class documentations are imho pretty useless.

What most of the time is missing - and what source docs don't cover - are practical, cohesive examples where not one, not two - but multiple things interact with each other and form a fully functioning system...

*cries in npm*

@IntrusionCM true that. I personally always look for unit/integration/convergence tests in a project just to have proper examples. I don't know the Java equivalents but usually a project that does not have Rspec for ruby/puppet, tox for python, molecule for ansible, is hardly not worth my time.

IMHO it comes down to real proper vetting of anything you're willing to use.

It gets better: turns out what I was missing was needing to set BOTH an "apikey" and "Authorization: Bearer" header value 😂🤡😂🤡😂🤡😂🤡😭😭😭

Neither were documented, I had to look into the source code's test implementation... at this point my soul is so gone I just don't care anymore, I've come to expect it.

@devRancid their anaconda length function names do the talking