What's a good replacement to "cookbook" as referring to general-purpose manual-like computer books?

Solution 1:

I'd say this word could be changed by either "Handy-book" or "Reference book". Although, cookbook fits amazingly with the context, due to the big amount of recipes which can be found inside these sort of books to avoid common issues.

Solution 2:

O'Reilly, being a book publisher, Tom Christiansen, being an author and a regular EL&U contributor, knows English well. There's a reason why they chose to call them "cookbooks" rather than the other terms suggested here so far.

The goal of the series is to provide short snippets of computer code that programmers can use to solve frequently encountered problems: these are called "recipes". These "cookbooks" assume that you are already somewhat familiar with the language, and just need prepackaged solutions for specific problems. For example, the PHP Cookbook would have a recipe for shuffling elements in an array. It contains a textbook implementation of the Fisher-Yates shuffling algorithm, which you can copy-and-paste into your program. There is an explanation of why the code works, and how it avoids common pitfalls when programmers try to implement their own shuffling algorithm.

Alternatives for "cookbook" just don't convey the concept of the book series correctly:

• It's not a "reference book". A reference book might list functions available in the PHP standard library, but not with an emphasis to teach you how to combine such functions to solve more complex problems.
• "Handy book" seems more like a description of O'Reilly's In a Nutshell series, or maybe Pocket references.
• "Bible" just replaces one metaphor with another less-appropriate one. A typical "bible" in programming consists of a tutorial followed by an appendix that contains a reference to all of the library functions available. (In my mind, these "bibles" are big, heavy volumes with lots of "filler" material that could be either more concise or would be better in an online format.)
• A "how to" book is too vague. It could, for example, be a complete beginner's guide to programming, with instructions for how to install a PHP interpreter, launch a text editor, etc.
• A "survey" could be an overly abstract treatment of the subject matter, discussing what features and packages are available, what the development roadmap for the language looks like, etc. In contrast, the O'Reilly Cookbooks provide very concrete advice for a wide variety of problems.
• A "manual" comes close. However, it doesn't have the same creativity implications as "cookbook": once you see how the example code works, you can be inspired to adapt the code to suit your needs when creating derivative works. Rather, following a manual implies a very strict process that discourages deviation.

Basically, "cookbook" is O'Reilly's answer to their own single-word-request.