No Documentation >> Un Organized and Shitty Documentation.

oh well that's just not true at all.

I was just working with an API that has a pretty shitty documentation, plenty of things are undocumented and I had to scavange forum posts to aggregate whatever knowledge people already figured out on their own to use it.

If the API was undocumented completely, I wouldn't even be able to use it in the first place, especially if it's close-sourced.

Shitty documentation still has information value, its just that a good documentation gives you everything you need to use the product, while a shitty one only gives you the bare minimum at best and wrong info at worst. Still a wrong info at least informs you, that a feature was or is available somewhere or in some way

@Hazarth i agree with you but im still reading this big documentation with some features explained and most of them not and it's really hard to understand.

It depends.
If the shitty documentation is so bad that you would be better off just reading the code, then no documentation is better than some shitty documentation.