David Barnes @ Packt

writing computer books that people want to buy 
« Back to blog

"Advanced Techniques"

I'm not that keen when books have a section of "advanced techniques".
 
Often "advanced" really means "hard to do". A book should show how to get a job done. If you need to know it, you have to cover it -- and the fact that its "advanced" makes no difference. If you don't need to know it, then you can either cut it out or -- if it's fun / useful -- include it near the end. Again, the fact that it's advanced makes no difference.
 
If you mean by advanced "optional, but useful". If that's the case, call it that. Or if it means "impressive stuff", then that's even better -- call it that. 

"Advanced" doesn't work well as a way to organize information because readers don't know if something is "hard" or not when they try to find out how to do it. For example: "Making my site secure". I don't know if that's easy ("basic techniques") or hard ("advanced techniques"). I just know I need to do it. So which part of the book should I go to for that?

What do you expect to see in the "advanced techniques" section of a book?

Comments (6)

Jul 01, 2009
etali said...
I'm used to 'advanced techniques' meaning things that could be slightly dangerous if you don't know what you're doing, but that could provide you with an extra benefit if done right.

I see the 'advanced' as a warning that maybe you shouldn't attempt whatever it is until you're sure you've understood everything else in the chapter.

Jul 01, 2009
Craig said...
Mostly, I expect to feel completely moronic.
Jul 01, 2009
Alfonso Romero said...
Well, I used to think "advanced" sections were for people that don't want to read the whole book, just pick up what they need because they already know how to do all the "beginner" stuff... but now that you mention it, maybe that's where a book should split up, one for beginners and one for advanced, that way maybe you could lower the price a little bit...
Jul 03, 2009
Milan Davidovic said...
Can you share particular examples of "advanced techniques" sections that you have in mind when you make this criticism?
Jul 03, 2009
David Barnes said...
Etali -- that is a good reason, I must admit. Oops.

Craig -- then you've come to the right place

Alfonso -- I like the sound of 2 books. As a publisher, not so keen on lower prices -- but I see your point.

Milan -- errrr, they all blend together after a while. If I spot any particularly egregious examples I'll get back to you.

Jul 03, 2009
Paul K. Sholar said...
These are the product features that provide power to the user but were not well thought out by the application's developers and so require a more verbose treatment in the documentation. It's not unusual for the developers to have gotten only so far in their conception of the product such that, around the edges of it features, the user must utilized half-measures,combine orthogonal features/syntax/concepts to accomplish something that is not easily presented by the product's interface.

This is an application problem of which the documentation's rough edges are a symptom.

Paul K. Sholar (Twitter: @bkwdgreencomet)

Leave a comment...

 
Got an account with one of these? Login here, or just enter your comment below.
Posterous-login    Connect    twitter