I don't know much about Apple developer documentation but I disagree with your comment. The following is a quote form the article > Given what I know of Apple

I don't know much about Apple developer documentation but I disagree with your comment. The following is a quote form the article > Given what I know of Apple’s approach to this, the problem is not individual engineers — who are not responsible for writing docs; that is the responsibility of dedicated coumentation teams. But that does not make it any less a failure of Apple’s engineering organization. The job of an API engineering organization is to support those who will consume that API. I don’t doubt that many of Apples API engineers would love for all of these things to be documented. I likewise do not doubt that the documentation team is understaffed for the work they have to do. (If I’m wrong, if I should doubt that, because Apple’s engineering culture doesn’t value this, then that’s even worse an indictment of the engineering culture.) This kind of thing has to change at the level of the entire engineering organization. It would be shameful if the author were calling out a particular person, because we do not know anything about any particular person who worked on these docs, what state they were in before that person got there, and what road blocks they might have. However, it is not shameful at all to call out Apple as a company. The assumption is that if any company in the world has the resources to make their documentation amazing, it is Apple. The failure is not that of the people working on the documentation, it is that of the company as a whole.