How to start understanding various documentations?

Question

Documentation

Hello! I have eternal problems with reading technical white papers. Take, for example, the same developer.apple.com, I open the documentation, for example, on UICollectionView, I start reading (with a translator, since I am only working on English) and I understand that it is difficult for me, I am looking for information in alternative sources. The best way I can figure it out is with the help of video tutorials on Youtube for example. The same situation with other documentation, Apple gave as an example. Has anyone had a similar experience?

Answer 1

First you need to determine what exactly you do not understand: the meaning of individual words or are all the words familiar, but they do not add up to the big picture? In the first case, you need to scrupulously study the relevant definitions. If there are unfamiliar words, then study them too, and so on. In the second case, you need to download such a skill as logic. Well, English, of course, since Google translate writes nonsense in difficult cases and almost always in technical documentation.
Understanding a documentation section starts with the title. It is usually meaningful. For example, UICollectionView is UI + Collection + View. Each word separately is worthy of a separate article, or even a book. In general, it is more or less already clear what will be discussed.
What follows is a short description of what it is. Although it is already obvious, a clear definition is given for those who doubt their guesses.
Then the technical details, where the API components are mentioned - what it is, how it is declared, what parameters (if it is a function), what type (if it is a property), etc.
Well, then everything else. Depending on the topic, there may be specific subsections, examples, links on the topic, a compatibility table, etc.
Your example represents a class, so the article lists all functions, properties, dependencies, etc.