in

ASP.NET Weblogs

Datagrid Girl

Marcie, ASP.NET Datagrid Blogger Girl

Multi-Author Books

I just bought a SAMS book, and it has 14 authors, 8 editors and a team coordinator.  What is the world coming to. Seriously. Does anyone else think this is overkill?

--Marcie

Comments

 

Wallym said:

How would you change things? Fewer authors would mean more pages per author. With schedules shortening, that does not seem likely. Publishers want the authors to do more work for less money. That doesn't seem fair. 14 is probably too many, but 2 would be too few. Must be a happy medium somwhere.....

Wally
June 18, 2004 2:01 AM
 

Rob Windsor said:


I was always a big Wrox fan until they started having the "author per chapter: books. There was no flow at all, it was like reading a bunch of magaine articles bound in book form.
June 18, 2004 2:09 AM
 

Josh said:

I guess you would need a team coordinator with that many authors and editors...That many authors would seem like it would create a very difficult to read book unless the editors did a very good job.
June 18, 2004 3:34 AM
 

Julian Gall said:

It's not the number of authors that bothers me but the number of pages. The best books I have seem to cover their subject in a couple of hundred. But publishers appear to like 800+ page blockbusters. Perhaps it's the need for so many pages that requires so many authors.
June 18, 2004 6:46 AM
 

SBC said:

I have Wrox's Prof XML (2nd Ed) that I picked up from Borders for a dollar (clearance sale) - the book has 13 authors! I wonder why Wrox went out of business..
June 18, 2004 11:42 AM
 

Nish said:

Definitely over kill! In fact the book prolly wont be much fun to read as it wont have any style of its own.

Nish
June 18, 2004 12:19 PM
 

Eric Engler said:

I think it'd be great if someone actually editted the books before publication. Lots of recent books have had sloppy editting.
June 18, 2004 3:56 PM
 

Kev said:

Precisely the reason I stopped buying Wrox books or those huge Unleashed/Special Edition/Bible things. The problem with having so many authors is that the core substance of the book becomes diluted and confused. You also stand in the bookshop thinking..."if I could just tear out this chapter because thats all I need".

Before the demise of Wrox they started to bring out their 'Handbook' series on specific topics - Code Security, Data Security etc. I thought this was a cracking idea. No more 1200 page(/Lb) bricks of paper to plough through to collate the knowledge I required to do a specific task - it was all gathered together in a single pocket sized (almost) format.

Big chunky books are fine if they're single topic but when they try to appeal to all and sundry and have a busload of authors then I just won't buy them.
June 18, 2004 5:50 PM
 

David Totzke said:

How the hell am I going to collect FOURTEEN autographs!?!
June 18, 2004 6:09 PM
 

Rob Hudson said:

I agree about the editing -- I was a tech ed for Wrox and couldn't get past the atrocious grammar to the technology!

Multi-author books would be fine assuming that the "team coordinator" was an actual professional *writer*.

That way the book would have a more consistent approach and readability.
July 1, 2004 3:19 PM

Leave a Comment

(required)  
(optional)
(required)  
Add