How to read books on programming?

Question

Java

What is the right way to read programming books (which are aimed at beginners)?
After 40 minutes of reading, interest is already lost, a simple absorption of the theory, and tasks only at the end of the chapter (without reading to the end of the chapter it is impossible to solve these tasks, and the chapter itself is 30 pages long).
How to read correctly so as not to forget what I read at the beginning of the chapter and interest in this book does not disappear (especially those books that I read contain 1000+ pages each).

Answer 1

first there were questions "how to become a programmer"
then questions "what to read"
now "how to read"
maybe soon it will be "how to learn the alphabet, otherwise my parents write on the toaster for me".
For books - read the simplest tutorials and immediately practice. Difficult books - later, when there is already a base in the head.
I'll add another point:
Read the article megamozg.ru/post/10126
It is very clearly stated that the professional skill and pain of a programmer is hyper-concentration, which is necessary to master the concepts and things for professional work. 40 minutes is kind of a no-brainer.

Answer 2

After 40 minutes of reading, interest is already lost, a simple absorption of the theory, and tasks only at the end of the chapter (without reading to the end of the chapter it is impossible to solve these tasks, and the chapter itself is 30 pages long).

The best way to remember is to start putting it into practice. But if this is not possible, then you can do this: come up with and write down questions as you read, the answers to which are in the book and which you want to remember. Next time, before you start reading again, go over and remember the answers to the written questions. Questions can also be written down on paper, but I prefer to do it on Wunderlist .
You can also see:
How to read technical literature quickly and productively?
Literature, about how to read books?
How to force yourself to read books on programming?

Answer 3

look for another book

Answer 4

You can focus on a book for 40 minutes, which is very good in my opinion. Read a book for 20 minutes, and do 20 minutes, program, try, make mistakes, but act.
The brain will switch.
In the process of programming, feel free to look ahead of the book, in those chapters that you have not yet read, but where, in your opinion, the answer to your questions may lie.
Come up with an interesting challenge. It is very important that the task arouses your interest. This interest in the task will serve as the engine of your learning.
Break the problem down into small chunks and solve it with the language/technology you are learning. If you have a problem while implementing some small piece of the program, and there is nothing about it in the book, then ask on forums like stackoverflow.com
I should note that when posting questions on such forums, if you want a quick answer, formulate your questions as correctly as possible. Explain the task that you are facing, be sure to show the code with which you tried to solve this task. And write down what you can't do.
If English is difficult, then there is StackOverflow in Russian: ru.stackoverflow.com
This is much more effective than studying a book in "boring" mode. Reading the theory, then doing the exercises.
Good luck.

Answer 5

better to outline.
write codes on a piece of paper and try to come up with intermediate tasks or look at tasks regularly. you can search jobs by "your language"

Answer 6

Programming books usually have a lot of examples. Interrupt each example, run, try to change something. So it is remembered better and interest will not be lost.

Answer 7

I will note such a phenomenon in the human body that after 45 minutes the concentration dissipates - this is a signal that you need to take a break for about five minutes, and even more so from a book when you sit still. If after 45 minutes there is no desire, ask yourself the question - why are you reading this book?

Answer 8

First, read interesting books.
Second, write down everything that might be important.

Answer 9

I take it you're learning programming to do nothing but form-slapping? Alas and ah, after reading 30 pages, you will not write a new game engine or music player. You need a base, a base - this is the very theory. You don’t need to write down anything anywhere, there is always Google at hand, and indeed, if this is an important topic, then the material that is presented in it will be used more than once in the course of the book.

Answer 10

If it's boring to read, go to courses, and not online, get some basic practice there, in the form of homework or projects (here the better the course, the better the tasks are selected). There is little theory in the course.
As for me, this is not to overcome this boredom, programming is still a boring thing if it does not help you explore and explore the world.
PS At school, biology was a boring subject for me, because then it prevented me from learning the world with its set of tools, now I study it, because it can be useful in understanding the world around us at the moment. It seems to me that in those days, no motivation would have worked for me to start learning this biology.

Answer 11

You only need to read theory books. In some cases, you need to read the documentation, although in 95% of cases it is enough to look at code examples. On form-slapping, you need to watch video tutorials, this is pure practice.
Books on theory should be read only when there is clearly a practical need for them. In this case, the theory does not look dry. This is not physics

Answer 12

I’m a beginner, so don’t beat with sticks) I
watched a video interview on the IT Beard channel and heard good advice: “Technical literature should not be read from cover to cover, but as a reference book. There is a question, open the table of contents, look for a topic, read, look and apply” .
Personally, this is how I read Java Philosophy.

Answer 13

Lost interest after 40 minutes of reading

I try not to read for more than half an hour, although everything depends on the book: I’m ready to read some kind of Head First all day
reread

Answer 14

Why read if there is no interest? Learn only what is really interesting to you. Maybe programming is not yours, but you are forcing yourself

Answer 15

30 pages?
HORROR!

Answer 16

how how. Well, at least 100 times you need to read .... and maybe 1000+ times. You don't become a programmer in a day, I'll even say that you won't become a programmer in a year.