共用方式為

One reason why I haven't been writing books

  • 發行項

Charles Petzold's latest post on books as long format tutorials vs. reference material hits the nail on the head.

In a nut shell, there are a lot of books out there, and people are relying on them less and less as search engines become the dominant way to find information. It's pretty hard to pour massive amounts of work into something when you know most people just want the code snippet that gets them past their current problem. No actual learning required.

Comments

  • Anonymous
    December 14, 2005
    ...and then they have no idea how the code works, so cannot adapt it to new requirements, or debug it when it doesn't work.

    To me, a good tutorial is worth a thousand times a code snippet - although I do find that often MS Press books (at least, of a certain vintage) will print the entire source of a sample program which leads to the new stuff being lost among the boilerplate.

    How new Windows programmers are supposed to learn what's going on when truly excellent books like Jeff Richter's "Programming Applications for Windows" go out of print I don't know. All abstractions leak, and I think you're better off understanding what leaks through the abstraction.
  • Anonymous
    December 14, 2005
    What I want is in-depth explainations of how thngs work... not snippets of how you do things that are "so yesterday"
  • Anonymous
    December 14, 2005
    AFAIK books may be divided into several kinds.
    For example books that describe some API are based on reference materials.
    In these books, indeed, there will be a lot of code snippets, which can be found in the Internet. They also describe common approach to solve problems with this or that API

    Another type of books are more analytical, contain more theory than practice. Yes, they also contain snippets, but have large amount of analytical info and theory that can be learned and used in the future...

    So, every book has its audience :8-)
  • Anonymous
    December 14, 2005
    Matt, I don't agree with you. Using search engines you can find small pieces of information related to your query. A (well written) book gives you a path to follow, from beginning to end. I've never found a place with the amount of well organized information I can find in a book. Every time I find a very good amount of information about a software in the web, it's the html content of a book or the product documentation (MSDN, PHP documentation, etc).

    We have still have Code Project, but no website have more information than your (or Petzold's) book. Keep writing :-)
  • Anonymous
    December 15, 2005
    The comment has been removed
  • Anonymous
    December 15, 2005
    I agree. Most people in my team will simply go to google/codeproject and keep searching until they find the exact snippet they need. This is more true in the case of people who write managed code (purely my observation!). The emphasis seems to be on getting the work done (even if it means copy - pasting code) without the need to gronk around at OS / platform / CPU level.

    But then there are a few who still love to read Matt Pietrek's and Jeffrey Richter's books on Win32 programming. We love life deep in the trenches :-)

    (Side Note - PEDUMP has been a life saver for me. Can't thank you enough for it. It actually inspired me to download the PE/COFF file format specification and write a similar tool.)
  • Anonymous
    December 16, 2005
    Don't forget though -- there are plenty of people out there (myself included) who like having a hard reference to read. When given the choice between reading something in electronic format (online, PDF, etc) or buying a book, I buy the book every time.