Answer the question
In order to leave comments, you need to log in
Books vs office. documentation vs articles vs video courses: what is the best way to learn a new technology or framework?
Interested in how best to self-learn a new technology, now at the intermediate level of html, css, javascript, taught almost everything in video courses. I started reading a book on JS, and somehow I don’t know, everything is going very slowly, then I throw it, then I return to it again. Interested in how you learn some new library, the same jquery, just from the office. documentation, or read a book about it, or watch a video, or articles?
And yet, can someone recommend some English-language documentation on Javascript and JQuery for beginners? JS is of particular interest, since MDN is somehow too confusing for a beginner. Interested in English, I know about javascript.ru. For css3 and HTML, I found convenient documentation for myself, but js is not yet available, maybe someone from personal experience will tell you.
Answer the question
In order to leave comments, you need to log in
It seems to me, or do you position these methods of obtaining information as mutually exclusive?
My advice is:
According to the library or framework:
1. Architecture scheme and its understanding,
2. hello world (code) and analysis ("overlay") of the code on the architectural scheme.
3. Understanding the basic architectural "skeleton" of the application.
4. A quick look at the OOB (out-of-box / "out of the box")
functions 5. View the ability to connect plugins and a quick look at the current list and the functions they implement.
------------
Setting a task for yourself and the beginning of implementation on the studied instrument.
in the case of libraries, I look at examples to understand what this thing does and why it does it, then I get into the code and documentation;
in the case of frameworks, I look at some short guide or getting started, I get into the code and documentation.
Say, about a year ago, I dealt with a new thing for me - webgl, Wikipedia, articles on the Internet, examples, and sort of sorted out the basics. Then he began to write a primitive toy just to figure it out, and stopped there. Further, books would most likely go, a more in-depth study of the GPU architecture and the organization of the graphics pipeline, books on opengl, etc. Fortunately, I already knew some of this, and I only needed webgl to speed up the rendering of images on the client.
I can suggest a very fast way.
To get even faster:
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question