5 ms·
Jeff's points ring close to home. Last year I wrote O'Reilly's Redis Cookbook. Even though I love the guys at O'Reilly (I really do, these folks are amazing at
by fredoliveira 14y ago
Jeff's points ring close to home. Last year I wrote O'Reilly's Redis Cookbook. Even though I love the guys at O'Reilly (I really do, these folks are amazing at what they do), writing a book provides little direct return. It's a great experience, and I wouldn't say I regret it, but it is far less glamorous than what it might seem at a first glance.
There's a comment in this thread that talks about publishers as VCs - which is a correct assessment. Some books do well, some don't. These days, technical books are often part of the latter group, as the amount of information out there renders the vast majority of these books useless.
Would I write another book? Sure. In fact, I'm writing the second edition of Redis Cookbook now. However, my expectations are not high. I don't expect to make a ton of money with it. I just want the people who buy the book to be happy with the content, and to contribute to the documentation on Redis. If I make a bit of cash doing so, perfect.
- mathgladiator 14y agoIf you don't mind me asking; how much did it make?
- fredoliveira 14y agoNot sure I can go into too much detail, but I guess I can say the publisher made a sum in the low/mid 5-digits.
- haraball 14y agoI often postpone buying technical books because I know they will too soon be dated. Since you're an author and on the other side of the table, what are your thoughts on offering those who bought the first edition the second book at a good price? Or to sell the book with some sort of subscription, where later editions are available for the subscribers?
- fredoliveira 14y agoI agree with that completely. I'd love to see it happen. It's the only way it makes sense for technical books to remain relevant.