|
yep, we just flip to erm, the interesting bits. We find it very interesting when the uhm, lady engineers demonstrate erm, different configurations exposing their mmmm, various attributes.
-- modified at 2:01 Saturday 5th August, 2006
|
|
|
|
|
A good way to test new or unfamiliar territory and it's just interesting to see if various code samples in some of the tech books actually function. Produces some interesting results.
Thomas
|
|
|
|
|
At least to me it depends of the moment, the project that it’s bugging my mind and the mood. Usually when I get a new book I read it randomly, this let me have an idea how to classify the book. Then I save it o the bookcase and probably it can be there for eons. Then when I have a project that requires more research or deep knowledge, I go to the right book, and I read it from cover to cover only on the interesting bits. When I decide to develop or work on my skills of some specific technical area then I tend to read the book cover to cover not jumping any page and writing every single line of code and exercised them. Lately it’s being more difficult to do this and I tend to start and when I reach to the middle I have to change the subject and sometimes change the book.
I think the problem here is that is a multiple option answer for the question and not a single answer.
|
|
|
|
|
There should be "it depends"
I have done all of the answers depending on the subject, and the need. I have read a technical book on encryption cover to cover, but I usually skim to know the subject matter and then tackle specific jobs once I know the contents. As long as I know where to look for the solution I don't need to memorize it ahead of time, so I skim all our library to know what is where and then as problems come up go straight to the right book (or at least to the right series and then find it within).
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
I feel the same way about most of these polls... the things tend to be over generalized.
I would like to see more of the polls pose a problem and allow us all to suggest/work out solutions.
I guess that would be hard to do as a poll. I think I'm looking for more of a brain teaser type game we could play.
-- modified at 16:06 Monday 31st July, 2006
-- modified at 16:06 Monday 31st July, 2006
-- modified at 16:07 Monday 31st July, 2006
|
|
|
|
|
Dummies and "21 days" books should be excluded as technical books.
---
Shawn Poulson
spoulson@explodingcoder.com
|
|
|
|
|
does a normal book take 21days to read?
-Prakash
|
|
|
|
|
Possible : only if days are 240 hours long. That's my experience with such books.
|
|
|
|
|
I haven't seen one that meets that definition in years.
Marc
XPressTierSome people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson People are just notoriously impossible. --DavidCrow There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
|
|
|
|
|
I know a couple: Patterns of enterprise architecture. Highly technical, The internet a top-down approach. This book tells a lot about protocols and has quite some formulas for calculating the effeciency of internet connections.
I really hate those books 'in 24 hours' or '21 days' way too simple and they don't tell the interesting stuff
WM.
What about weapons of mass-construction?
|
|
|
|
|
When I have a new book I read it quickly (by eyes)
so, I have an index of it in my brain,
when I need a topic and can't get it myself, turn back to the book and read the topic.
When I have a time I choose a random topics to read.
IIF(Me.Brain.Active, Me.Title = "Solution developer", Me.Title = "Something else")
|
|
|
|
|
SpiriTwin wrote: read it quickly (by eyes)
That's the only method I've found to read, so far. I tried putting a book under my pillow and absorbing it while I slept, but it didn't seem to work.
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
Shred it and eat it with your morning muesli. Does wonders for digestion if nothing else.
|
|
|
|
|
So that's why instant oatmeal tastes so bad - it's made from shredded VB books! Even Soilent Green tastes better than that.
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
hehe. Try to more expensive type, I think it has books on phylosophy in it
Gotta love academic food...
WM.
What about weapons of mass-construction?
|
|
|
|
|
Some parts of a book must be read, first. Often first and second chapters containing basics and fundamentals of a new technology. After getting used to the technology, stop reading that way and try finding soloution to my problems.
//This is not a signature
while (I'm_alive) {
printf("I Love Programming");
}
|
|
|
|
|
You think you are reading a novel?
|
|
|
|
|
actually, i never read technical books on their paper form (pdf or html is good enough to pick the informations i want).
but i made it once, when i learn C++ with "The C++ Language"... i did it like this : cover to cover, from beginnning to end, reading each page, each paragraph, each detail...
well, at least, it was interresting
|
|
|
|
|
|
yes, i had done it. cover to cover, page to page, the gameoflife sample was my fav.
-Prakash
|
|
|
|
|
When I was learning asm, c++, xslt, I've read three books on them cover to cover, because one must know all tips and tricks to make something good. However I know something in .net and it works... somehow...
|
|
|
|
|
Weiye Chen wrote: You think you are reading a novel?
Sometimes[^] it does feel like it.
|
|
|
|
|
Such a happy ending...
|
|
|
|
|
A good book is read that way.
|
|
|
|
|
Naw, novels are properly read as in option #4...
|
|
|
|