Re:Announcing a Node.js Book Project
by jrockway on Tuesday November 09, 2010 @06:55PM
(#1888512)
People told me the same thing about my Catalyst book. "Things are changing too quickly, don't write a book."
If you don't write a book now, though, people are just going to use some other technology, and then you'll never have a chance to build a community of library-writers. The solution is to write a book now, then write another book when things are more stable! Early adopters shouldn't have to dive through the source code and ask questions on IRC; they should be able to read, learn, and begin contributing. Most people don't like being confused and scared when evaluating a new technology or programming technique; they need someone to hold their hand.
Incidentally, I was also told my book would not sell, but it sold thousands of copies despite various typographical (and technical, arguably) errors.
Don't not write a book because someone on the Internet told you it wouldn't sell or it would be outdated too quickly.
If you don't write a book now, though, people are just going to use some other technology, and then you'll never have a chance to build a community of library-writers. The solution is to write a book now, then write another book when things are more stable! Early adopters shouldn't have to dive through the source code and ask questions on IRC; they should be able to read, learn, and begin contributing. Most people don't like being confused and scared when evaluating a new technology or programming technique; they need someone to hold their hand.
Incidentally, I was also told my book would not sell, but it sold thousands of copies despite various typographical (and technical, arguably) errors.
Don't not write a book because someone on the Internet told you it wouldn't sell or it would be outdated too quickly.