#103 “Why don't developers read documentation? It's so important.”

I used to believe that by accomplishing more at work, extending skillset horizons and working harder that eventually will get myself into senior position. However, while working with seniors, I found something amazingly interesting: They don’t particularly know much better than a junior, they don't necessarily work harder than any other worker and they don't seem to be the person who knows it all. Instead, what makes them different when facing a new challenge/task is the way they react to it. It seems so natural and effortless to them, yet so trivial to others to even consider to begin with. Not even to mention how frustrating/overwhelming it can get for juniors to even think about statrting point. What is the magic behind this relaxed attitude?

The simple answer is that by taking something for granted like reading documentation serious again, up to the point that it's automatic for seniors to go to forums, official documentation when facing challenges. Even in the era of AI, grinding documentation is still highly valid.

Reading documentation like a pro

I do read documentation, but I do not know how to read documentation properly. I do have the option to read documentation, but I don't have faith in the outcome getting from reading documentation based on…