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?"
Moderators: That is a joke.
Sig (appended to the end of comments you post, 120 chars)
1. Teach yourself ANSI Common LISP in 24 hours.
2. The Complete Idiot's Guide to the Linux Kernel Internals.
3. Assembly language for Dummies
4. Giving yourself a Enterprise Java Enema.
called Teach Yourself Teaching Yourself In 21 Days In 21 Days
I can just imagine what a doubly linked list would look like. I'm afraid. Very, very afraid.
Personally I'd like to have hemp paper books. Hemp paper is of exceptional quality and a tonne of hemp will make much more paper then a tonne of dead trees.
That and I'd love to see some idiot try to smoke a book.
SELECT first_name,phone_number FROM women WHERE easy='very' AND looks='good'
---If you can't trust a nerd, who can you trust?