Although, there is no denying that this is a valuable resource  but I have started to get turned off by a list of n books to learn something - they can be valuable but it is undeniable that they can also be overwhelming and perplex someone about how to get started. I believe technical books should be used to complement your knowledge of the field not to get started in it. For eg, &quot;Secrets of the JavaScript Ninja&quot; will be very valuable because I already have experience in JS and it will help me understand some of the caveats that I might have overlooked. The best way has always been to get start implement something regarding the subject and try to dive into everything you uncover.<p>A blog post submitted here mentioned the same sentiment [1] -<p>&gt; I can’t fully explain how immensely unmotivating it is to be given a huge list of resources without any context. It’s akin to a teacher handing you a stack of textbooks and saying “read all of these”. I struggled with this approach when I was in school. If I had started learning data science this way, I never would have kept going.<p>[1]: <a href="https:&#x2F;&#x2F;www.dataquest.io&#x2F;blog&#x2F;how-to-actually-learn-data-science&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.dataquest.io&#x2F;blog&#x2F;how-to-actually-learn-data-sci...</a>