This is not a big mistake. This is something which all programmers do all the time Including me, and that is trying to skip the documentation and trying to work with new technology by yourself.
This is fairly common If you are working with tools or softwares, Not exactly a programming language. For example, like cloud service (AWS), softwares, softwares as a web-services kind of things. We just jump into the UI and start using it.
However, like Quote says that, "You can save lots of hours of debugging If you just spend 10 min of time reading the documentation". If you not reading the documentation you could be reading unreliable sources. you could be reading from old sources. If the documentation available, why not just go ahead and do that ?
My best practice is to actually take official documentation If it is available or else you can stick to video tutorial or playlist. But also have an eye on what the official documentation says.
** "Happy Learning". **
** -Raj**
Top comments (2)
That's true. I'm a kind of person who prefer the official documentation to other resources. But don't forget that we sometimes find a Stack Overflow thread explains much better and deeper than the official documentation. Sigh.
I prefer trial and error over reading documentation because that way you can stumble on stuff you haven't thought of. Eventually I will start crawling back to the official docs though, but generally with a typed language its pretty easy to figure out yourself, considering most things use the same patterns anyway.