The majority of newbies and even some experts in software programming often ask themselves a question: how to read a book on programming? They want to save time and get more effect from reading.
What do you think? Which of the following tips would be more useful?
- To read one chapter, and only after that to study a set of examples and task solutions.
- To read a chapter and a set of examples at the same time.
- To read a chapter / book and then review examples only visually, inventing own analogues of described problems.
We asked Oxagile programmers what do they think about these questions and got the following answers:
- I try to go read the chapter, type examples (I think that mechanical typing is also beneficial for me =), then I try to invent my own tasks for the given topic.
- Traveling by subway I saw bearded guy who was reading the textbook on C + +, desperately commenting tasks in his notebook. I like this approach to the effective reading, but sometimes it looks like fanaticism =).
- I start my reading from different parts of the book at the same time =). And in such a way my new book can be full of multicolored bookmarks even at the first day.
The way of reading depends on your way of thinking, so you can choose your own variant of effective reading. Good luck!