few ideas: * learning style: theoretical, hands-on examples, progressively build a project, enough to know how terminology is used/applied * relevent skil

few ideas: * learning style: theoretical, hands-on examples, progressively build a project, enough to know how terminology is used/applied * relevent skill level(s) before, skill level after using book: totally new subject to did phd thesis, to some mix/match various background related to 'programming book' * 'age / scope of content material': bleeding edge / getting up to speed / broading understanding of topic(s) area(s) such as general operating system concepts / narrow focus, such as using yacc / need to translate original 1950's fortran 1 into current object oriented fortran. ok, last one likely 2 books, unless new to object orient design, then 3. Perhaps 4 if need to build & program a diy punch card reader to upload the fortran 1 punch cards to a electronic file on usb drive, some interminate amount of parenthetical book references used to learn/build program(s) to convert a single picture of bunch of punch cards into ascii text file. * purpose for using the book: reference, support some programming project, use to help understand a project, using to suplement understanding of tools used in programming class