I'm making annotations with crayon in the books - or highlighting ebooks - when reading interesting things. That's usually how I'm remembering it later when the occasion presents. :-)
And skipping what I'm quite sure is not applicable to what I'm doing at work. I'm rarely reading a book cover to cover. But neither am I afraid to reread books when I need a refresh about a subject. On Tue, Jun 12, 2012 at 7:31 PM, Joe Attardi <[email protected]> wrote: > Hi all, > > What are some ways you effectively absorb knowledge from reading > programming books? For language or feature specific stuff, obviously > working on a project with it is the best way to learn. But what about more > general things - stuff like *Effective Java* or *Head First Design > Patterns*? > > Do you take notes while you read? Skim and reread for detail? Any good > tips to offer? > > -- > You received this message because you are subscribed to the Google Groups > "Java Posse" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/javaposse/-/erdZF4Sii-gJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
