|
"Send codez plz" works for me...
|
|
|
|
|
I crack open a book once and a while. Its good to give the ol' eyes a rest from the screen. I also feel that fundamentally its a better approach to build a foundation of knowledge on a development topic, as opposed to just binging your way around from the get go.
I have also been known to visit the local library on occasion. 
|
|
|
|
|
Depending on the layout I generally find it easier to read the "Book form" rather than Digital.
It would be nice If i could afford both the Digital and The book form.
You can print just some pages better with the digital form and do a string search for the exact term you are looking for.
Some of the layouts are just better in the book form and easier for me to follow.
|
|
|
|
|
I use textbooks sometimes, but more ones that cover processes/design not actual code stuff.
|
|
|
|
|
When learning a new subject or looking up detailed data about some algorithm (complexity etc.), I use a printed book. When looking up details (e.g. the syntax of the foobar command), I use MSDN or some such.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I use printed books less every day - and I sure miss them!
So, all the time I keep buying new textbooks when I need to learn something new. And I keep missing the old textbooks. Because technical authors these days write for the screen: Detached, disorganized and unstructured, incomplete. No natural progression, no concern about the reader, neither his real needs nor his background.
Lots of textbooks nowadays look as if the author has had a brainstorming, simply jotting down elements that he thinks the reader should know of, in the order they came to the author's mind. What didn't come to mind during that brainstorming, doesn't make it into his book. No atttempt is made to draw the big map, making the user understand what is really going on; it is more like trying to minimize the reader's level of understanding, relieve the user from 'having to' know. 'Just do exactly what I tell you to, and you'll be fine!'
I truly hate these dozens upon dozens of books with titles like "XXX in three days", "Set up a ZZZ in less than a week", "All you have to know about YYY" - plus all the books with different titles, but with a similar content.
I hate those books that tell the reader 'Type so-and-so and press Enter to complete the line', and then on the next page goes ahead telling the reader that 'You can find all the details of CSS if you google around a little'. I have never, ever, met a user who must be told to press Enter, yet capable of understanding how CSS is put together!
And finally, I hate those books that, judged from the table of contents, are seemingly well organized, with clearly defined chapter headings, so you can skip topics that - at least at the moment - are completely irrelevant to you (such as "Installing the system on an iMac" or "Translating to languages using non-Western character sets"), but later you realize that those essential details you spent hours finding on the Internet are included in the book, in that chapter on iMac installation: That's where the author made use of that facility. In no way is it iMac specific; in no way is it restricted to installation, and it is certainly not mentioned in the index section. You are forced to read through a lot of irrelevant stuff to make sure that you are not missing out on essential details.
What I miss is not the physical paper format as the cohererent, complete, well structured information that you could find in the old books. Nowadays, I have to buy half a dozen books on any given topic, read them all from start to end, and try to straighten out the mess myself. And then it is usually just as good picking up the pieces by googling.
|
|
|
|
|
Yes indeed! I remember reading Michael Abrash's book "Zen of Assembly Language" way back in the DOS days. It was like a "Zen of Motorcycle Maintenance" kind of book for understanding not just assembly language but also algorithms in general. I walked away from that book feeling like I understood more about my craft.
The same can be said of the famous Petzold "Programming Windows" books. I _knew_ how Windows programs worked internally, and knowledge of message pumps, device contexts, and the GDI still comes in handy today. More recently, I've been a fan of the APress Programming .NET books since they give a lot of detail that's not easy to find elsewhere.
I've noticed two trends recently though that disturb me. It makes me sound "old", but I really do think it's a generational thing. First, young programmers in our company turn to video instruction first, forums second, and books almost not at all. It's fine for a superficial understanding that allows you to get work done, but until you really grok the async framework (speaking .NET here), lambdas, and so on it's difficult to work with existing code so lots of stuff gets duplicated. Second, it seems like our profession is more willing to put up with copy-and-paste code from Stack Overflow answers than it has ever been. Tons of people who couldn't code themselves out of a box are writing software for large corporations by pasting in the work of others and messing with it until it has the appearance of working. This "good enough coding" style is what makes business folk think we're all easily replaceable and that coding is super simple.
At the end of the day, I blame big business for killing off the book. Doing things right and avoiding obvious security flaws just isn't important to stakeholders anymore. That's why we're _still_ seeing SQL injection attacks in 2016... Technical instruction is now aimed at the copy-and-paste people. The market will follow the consumers, and us book-reading folk no longer represent the majority.
|
|
|
|
|
I tend to buy the Kindle version of a book, if it's available. More and more are being provided that way. It's a lot cheaper for a start.
|
|
|
|
|
I've not read paper documentation since I worked in 68k Assembler on an Atari ST...
My first proper gig was on a Mac using Metrowerks CodeWarrior to build image manipulation apps for pre-press. Came with 'Inside Macintosh' - on two CDs.
I miss books though. There's something really comforting about having pages open next to you that you can flick through, dog ear the corner so you can find it again, and make notes in the margin and such.
Halcyon days...
Danny
|
|
|
|
|
I rarely use paper manuals; they occupy too much space  I love Safari Online, and Google (*enter your own preference*) can be a good friend too. The only problem with searching online is that one needs to sort the wheat from the chaff too much.
|
|
|
|
|
Only if vehicle service manuals count as tech manuals For whatever reason, it's much more pleasant to have a hard-copy manual to refer to when working on my cars.
|
|
|
|
|
|
I have over 1180 "technical" PDF's; filed in about 120 "categories"; from "Access" to "XNA".
I'll load a couple of categories on my "mobile" depending what I'm working on.
With indexes, bookmarks and the ability to "highlight" passages, "books" are a still a great resource.
(I am considering throwing out my Funk and Wagnall's. Can use the shelf space.)
|
|
|
|
|
but I ended up just creating something in python faster because I am more proficient in python. I wanted to teach myself something new.
|
|
|
|
|
Only if I'm perusing something interesting, like Beaglebone development.
Other than that, no, Google is my friend!
Marc
|
|
|
|
|
Yes I do. For an overview a book beats anything online . Online is good for a very specific question. How should I put it? A book is more panoramic. An old saying goes,"Miss the forest for the trees.". You can scan differnet pages very quickly.
It is really a question of which is most appropriate in a given situation.
A may add that that is a problem of our age. Missing the bigger picture with an obsessiveness that excludes all else. Like the current polarised views of politics, etc.
|
|
|
|
|
Is a smiling soothsayer just a happy medium?
(Sorry it's early, Herself has an appointment with the Dentist, so I need the time to find the whip, straightjacket, handcuffs, big first aid kit, splints, and A&E telephone number)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: (Sorry it's early, Herself has an appointment with the Dentist, so I need the time to find the whip, straightjacket, handcuffs, big first aid kit, splints,
Making your most of the time with the Sheep whilst she is out of the house?
|
|
|
|
|
That lot is the minimum requirement to get her into the dentist's office.
She's getting better - ten years ago I needed a taser as well... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Not sure, but I know a dwarf soothsayer on the lam is a small medium at large.
/ravi
|
|
|
|
|
I shouda seen that coming!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
That's what she said. 
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
Politically incorrect response? +5!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
My soothsaying company went bust - there was no prophet in it.
I am not a number. I am a ... no, wait!
|
|
|
|
|
Early bird you are, but you still do not sound like a tarot! 
... such stuff as dreams are made on
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
