|
a lot of chapters of diferent books, webs, online manuals, help files, forums / online portals...
In my opinion a full book is the best option when you need to learn something completely new and you have the time to slowly read it or (if the book is a really good one) to get a deeper know-how about something specific.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Exactly! I don't remember completely reading a programming book. 
..Go Green..
|
|
|
|
|
|
I don't need to remember, the answer is... never
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
..Go Green..
|
|
|
|
|
I though video tutorials were the "in" things.
(Though nothing can beat a good book IMO)
|
|
|
|
|
Possibly, watch a few tutorials, grap a Ruby distro - and you are suddenly a "professional" ... sounds so easy it must be true, or ... 
|
|
|
|
|
I absolutely detest these - too often I get frustrated with the slow pace, coverage of stuff I've already seen. With a book I can skim through sections more easily, they typically have indexes and contents, and (if in digital format) can be searched. Try that with a video.
To me its just software companies to lazy to employ writers.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
If asked how many books read cover to cover my answer would be "none".
But I read several chapters in several books to get the basics of several technologies.
|
|
|
|
|
Exactly, the question is a bit to vague by what they mean by 'read'. I've read well over 24 books, but cover to cover? Probably only 1 or 2 at the most.
Generally if you are new, you may read a dev book cover to cover, but most of the time they are used either as a reference or to 'fill in the gaps' by reading pertinent chapters and skipping stuff you already know. And I almost always skip the 'history of' chapters!
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone - Bjarne Stroustrup
The world is going to laugh at you anyway, might as well crack the 1st joke!
My code has no bugs, it runs exactly as it was written.
|
|
|
|
|
I'm afraid I've become a selected chapters reader... 
If there were no magazines and online articles I would live in a state of lasting ignorance.
I've read only one complete book this year, but finished one I've started reading two years ago  .
Mislim, dakle jeo sam.
|
|
|
|
|
I am more interested these days to read short and crispy technical reports. What I understood is that these tinny technical articles are combined and elaborated to create lengthy bulk books
And I really love to read these as print-outs, rather than as softcopys'  . Yeah, yeah I know that I am wasting paper ....please pardon me. Old school habits 
|
|
|
|
|
I'd say, if you've read more than 0 books lately you probably are either in the publishing/writing business, or just beginning your dev road (student, nuby etc)
Most developers find it hard to read all the way though the post they've found in google that solves the problem they currently face.
It is a paradox that paradoxes would actually exist in reality.
That means of course that they don't exist.
However, they do!
∫(Edo )dx = Tzumer
∑k( this.Kid) k = this. ♥
modified 29-Jul-13 1:22am.
|
|
|
|
|
I absolutely disagree, I've been developing for over 25 years and still like to read regularly to exercise myself and keep up to date.
Recent choices are The C++ Programming Language (new edition, to get familiar with modern C++ again) and Real World Haskell (to try and get into true functional programming)
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
