Some book suggestions over here: Four books professional developers should read (and a few you don’t need to).
This is great: HackerNews Readings. It’s a listing of 40,000 books recommended on Hacker News.
This dude Gareth Branwyn has a few interesting books.
Some links on the concept and practise of reading text books:
- Six Reading Myths
- 3 R’s for Academic Survival
- SQ3R Method for Thorough Study
- Getting to Know Your Textbook
Six Reading Myths
- I have to read every word
- Reading once is enough
- It is sinful to skip passages in reading
- Machines are necessary to improve my reading speed
- If I skim or read too rapidly my comprehension will drop
- There is something about my eyes that keeps me from reading fast
3 R’s for Academic Survival
Here is a lean and wiry system containing all the essential techniques for mastering textbook assignments. This is an “exam passer”.
Read the chapter paragraph by paragraph. Read and re-read until you can answer the question: “What did the author say in this paragraph?”
Once you are able to describe what is in the paragraph, you will want to retain that learning by underlining, making notes in the margin, or making notes in your notebook.
Cover up your notes or printed page and recite aloud. Remember! If you can’t say it now, you won’t be able to say it tomorrow in class, nor write it in a week on an exam; so while you still have a chance, try and try again, until you can say it.
SQ3R Method for Thorough Study
Look over material critically. Skim through the book and read topical and subtopical headings and sentences. Read the summaries at the end of chapters and books. Try to anticipate what the author is going to say.
WRITE these notes on paper, in sequence; then look over the jottings to get an overall idea or picture. This will enable you to see where you are going.
Instead of reading paragraph headings such as “Basic Concepts of Reading,” change to read, “What are the Basic Concepts of Reading?” These questions will become “hooks” on which to hang the reading material.
WRITE these questions out; look over the questions to see the emphasis and direction; then attempt to give plausible answers before further reading.
Read with smoothness and alertness to answer the questions. Use all the techniques and principles demonstrated in class.
WRITE notes, in your own words, under each question. Take a minimum number of notes-use these notes as a skeleton.
Without looking at your book or notes, mentally visualize and sketch, in your own words, the high points of the material immediately upon completing the reading.
- This forces you to check understanding.
- This channels the material into a natural and usable form.
- This points up what you do not understand.
- This forces you to think.
Note: More time should be spent on recall than on reading.
Look at your questions, answers, notes and book to see how well you did recall. Observe carefully the points stated incorrectly or omitted. Fix carefully in mind the logical sequence of the entire idea, concepts, or problem. Finish up with a mental picture of the WHOLE.
Getting to Know Your Textbook
- Examine the title page:
- Who are the authors?
- What is their standing in their fields? (Perhaps you can ask your professor.)
- Do their training and background qualify them to write a book of this type?
- Who are the publishers?
- When was this textbook published? What does that tell you about the book?
- Examine the preface or introduction:
- Why is a preface written?
- What does it tell you about the book?
- Do the authors introduce any unusual features of your book in the preface and prepare you to be on the lookout for them?
- Examine the table of contents:
- What does the table of contents tell?
- How is this textbook organized? What main divisions has it?
- Compare the table of contents with that of another book in the same field. Do the two books cover the same topics? Are these the topics you expected to find covered in this text?
- Examine index, glossary, other material at the back of the book:
- How does the index differ from the table of contents? How does it resemble the table of contents?
- What sort of topics should be looked up in the index instead of the table of contents?
- What are cross references?
- Is there a glossary in your textbook? Can you use diacritical markings successfully to pronounce a word?
- Is there an appendix in your book? Why isn’t this information included in the body of the book? How would it have affected the organization?
- What is the literal meaning of “index” according to the dictionary?
- Examine study questions, guides, and other helps:
- Does the text provide study aids to help in understanding the text?
- Are the study aids in the form of questions, exercises, or activities?
- If questions are used, do they simply require finding the answers or must you do some critical problem-type thinking to arrive at answers?
- Are there study aids both preceding and following a chapter? Which types of aids help you most?
- Does the text provide suggestions for other readings or materials designed to help you understand this chapter?
- Examine chapter headings, sectional headings, and margin guides:
- Look at the chapter heading and then the section headings that follow. Write them down and see if this gives an overview of the chapter.
- How do headings help in skimming a chapter for specific information?
- Do you find different kinds of type in your chapter? Does this help you understand the organization of your textbook better? How?
- Does the text provide help in identifying material to be found within each paragraph? Is the topic sentence indicated?
- Does the book use summaries? How do these help? What is the difference between giving the gist of a chapter and summarizing its contents?
- Examine maps, pictures, charts, diagrams, and tables:
- Which of these visual aids is used? Do you understand them?