Thank you for your sincere words again, Sebastian!
In my experience I'm not able to create for example, any project by just reading the documentation (as a lot of documentation is poorly explained and lack in useful examples), so I often explore many courses and create my own projects after my doubts were clear and answered.
I agree that problem-searching by yourself will teach you a lot, but I've seen myself googling through responses that weren't useful or were outdated and I think that's a problem when trying to do something from scratch.
Although I found out that sometimes it is better to first understand, study, and then do, because the 'but it works!' doesn't mean always that it works correctly...
Thank you again for sharing your experience!
I concur, these are problems i have faced as well. :)
In regards to bad documentation, a good tip is to learn how to dive into the source for answers.
It seems daunting at first, but after a few dives it becomes more manageable, the quicker one learns this habit the better, as it lessons your reliance on explanations prepared. On top of that it teaches you how other people write code.
Sometimes, the problem of documentation. It is cumbersome to find her. The solution is Zeal, DevDocs, Dash o Velocity.. You can even include this within your editor such as in Visual Studio Code 🙈
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.