Despite the "incomplete and frequently wrong" nature of documentation, I still think a careful reading of that documentation is probably the best place to start.
If it doesn't hold the answer, fine, we can look elsewhere. But it does hold the answer often enough that reading that funny manual first all the time will save time over the course of a career.
If it doesn't hold the answer, fine, we can look elsewhere. But it does hold the answer often enough that reading that funny manual first all the time will save time over the course of a career.