3 ms·
I liked the O'Reilly days. MDN is good, especially as a reference to refresh something I once knew but haven't used in a while, or to deepen my knowledge of so
by tzs 6y ago
I liked the O'Reilly days.
MDN is good, especially as a reference to refresh something I once knew but haven't used in a while, or to deepen my knowledge of some part of something I do know fairly well.
But when it comes to learning something new and big, I often get lost on MDN. After I finish reading one page, it can be unclear what page I should read next. After I've made a few such choices and seem to have reached the end, it is often not clear if I've really covered the topic or there might be more if I go back several steps and make a different choice.
In the O'Reilly days, to learn topic X I could just get "Learning X" to get the basics, then "Programming X" to get a deeper understanding, "X Cookbook" for a ton of examples, "Advanced X" to go even farther, and maybe they would also have some more specialized books covering the use of X in specific applications. There might also be more books between beginner and advanced for some topics. And maybe an "X Reference". (There was also for some topics "X: The Definitive Guide" which tended to be a massive book that kind of tried to cover from beginner to advanced in one volume).
There would be an O'Reilly book aimed for people at whatever my current level of X understanding was, and reading that book would take me up a level.
There's no reason a website can't do that too, but it doesn't happen automatically. The website needs to provide guidance to lead the reader through in a page by page sequence that will take them through some topic in a way that makes sense and is complete. It's way too easy for a site to end up with a lot of ways to wander off such a path and end missing things or getting things in a confusing order.