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

Definitely want dead tree books

[wiredog]

It's hard to write notes on the margins of an e-book. Hard to read one of those while eating, since I don't eat at my computer.

What kind? Zope, and other web application servers are an area of interest. Hmmm, sorry, can't think of any other interests that aren't met by the Books With The Animals On The Covers. Heck, I've got 5 of those within arms reach right now.