Apr-23-2020, 06:25 PM
I think the major downside of all the sources to find information is the fact that they usally use examples, which are not necessarely explain what you want to do. But that is not really the goal of that type of documentation I guess. But on the other hand, what's wrong with getting an idea of something and then explore further? When you think of what your goal is with your code you can get inspired by these sources. And as soon as you have the idea that, for example a specific library, suits your situation you can try it yourself and read the official documentation.
I usally recommend to read that anyway, especially to get an idea of the different kind of functions it provides. I do this a lot when working on my linux machine. In that case I always use the 'man pages', get inspired and just try things out. After all, you will need to try whatever is possibly enriches your coding skills.
I usally recommend to read that anyway, especially to get an idea of the different kind of functions it provides. I do this a lot when working on my linux machine. In that case I always use the 'man pages', get inspired and just try things out. After all, you will need to try whatever is possibly enriches your coding skills.