Although you certainly have a point, the core problem is often that the documentation is poor.
A not uncommon problem being "solutions" which omit steps or assume that everyone knows how to find, what is in practice, an obscure option. Sometimes also having "boilerplate" which overexplains another part of the process.
Amazingly, security libraries are often in this category. Is there a really good writeup ANYWHERE about SSL, certificates and signing practices?
That would also have to include TLS, STARTTLS, how it can really be STARTSSL, etc. There's also the issue of what is actually part of the protocol and what is implimentation specific.