What Kind of Books do You Want?

ctrimble asks: "I'm the acquisitions editor for a technical publishing company (not the one with the animals, but we have had six of our books reviewed favourably, here on Slashdot) and part of my job is to determine what books my company should publish. This consists, mainly, of me sitting in my apartment eating peanut butter sandwiches, reading Slashdot, and writing perl scripts that generate titles in a Madlibs type fashion: "Hacking Ruby for Midgets" (forthcoming in July). Unfortunately, there's a bit of an impedance mismatch between my methodology and filling the needs of the programming community. Market research is tough to do in tech books since you need to forcast about a year in advance. So, let me pose the question to you -- what kind of books do you want? What spots do you see as needing to be filled? For that matter, do you even want dead-tree books, or are eBooks and/or online documentation sufficient?"

Comments

Pr0n

[selectspec]

Pr0n sells. Everything else is a complete waste of time. However, why not mix tech manuals with the Pr0n. Or at least replace the animals on the cover with naked ladies: a different naked lady each time. Here are some titles:

"Perl 6, and some good Pr0n because God only knows that you'll never get a date with this book."

"Embedded Systems Programming and Full Frontal Nudity, because this topic is too boring to sell on its own."

etc.