Ask HN: Have you written a book?
I bet a lot of us have, since this is a group that is inclined towards A) intellectual pursuits, and B) making cool things. I'd be really interested to see what kinds of books we've all made. They don't need to be published through the traditional process. In fact, I'm actually more curious to see creative ways good hackers have gotten their ideas out there.
So, if you've written a book, would you link to it and talk a little bit about what it's all about?
55 comments
[ 5.0 ms ] story [ 127 ms ] threadThe idea was to create a Think and Grow Rich type of book for bloggers and writing types, but I'm not sure we executed as well as I wanted to. I think it reads well and a lot of people have enjoyed it (Sold around 750-1k copies to date), but it's on a topic I'm no longer interested in so I'm probably biased against it.
That being said, most of the people we featured in the book continued to be successful, so I'm proud of that (that we chose well).
Was also great to interview people. We had interviews recorded for the 2nd book (including Seth Godin, Andrew Warner, Mitch Joel, and 10 others), but opted against it.
Was a great experience though, and I not only enjoyed writing it, but also enjoyed the pieces of the publishing industry that I was able to experience.
http://journal.dedasys.com/2009/09/15/tcl-and-the-tk-toolkit...
It has left something of a bitter taste in my mouth though... I've made an order of magnitude more money from this article that took my a few hours to put together: http://journal.dedasys.com/2008/11/24/slicehost-vs-linode as compared to weeks of work for the Tcl one.
Also, on the subject of authorship, I would be remiss if I didn't link to my latest project, a system to make the Kindle book production process as easy as possible: http://www.liberwriter.com
I originally put it together because I wanted to write something of my own, but I'm more of a hacker than a writer, and got sidetracked growing the program and still haven't got back to the writing.
It's not as cool as using an API, nor as efficient in some ways, but it works for Word, OpenOffice, whatever, and it's very simple to explain to the target market for LiberWriter (hint: it's not people like Daniel Markham who go out and download the spec:-)
There are a few books about the XMPP protocol itself, but I really wanted to see something that was more about how to get things done with it than schema descriptions. The book has a multiplayer game, collaborative whiteboard, shared document editor, and the usual chat-inspired examples.
People seem to enjoy it, and I had a lot of fun writing it.
For folks who have suffered under various Agile, Kanban, and other improvement regimes and know that it's not supposed to be like this.
I'm about 80% of the way through the first draft. I have a few prominent community members that are going to review (and recommend, if they like it) but it's more of a personal statement than a commercial venture. It's a topic I have a lot of experience in, and the neat thing about a book is that it's there and can provide assistance for a long time.
I plan on taking my time finishing it. I'm also a self-publisher, so I had to learn epub and the ins and outs of self-publishing. There's a lot more to learning that stuff than I suspected. Probably enough for another book.
The website isn't up yet. Email me if you'd like to be on the notification list. (Obligatory cool 3-D book cover image http://www.whattofix.com/ak2%203d%20book%20image.png )
Then there was the question of who to send the book to -- once it's done, where does it go? And, if you ask me, it's very easy to get screwed as an author.
There are about a dozen different decision points you have to go through -- format, topic, compatibility with other formats, distribution, marketing, sales, etc. Each of these is non-trivial.
For instance, you could just offer folks your book from your web site. Click the button and get a download. But do most people know how to take a download and put it on their e-reader? Are you sure you want no DRM at all? Which vendor do you want handling the mechanics of the sale, if any? If you offer a download from your site, does it preclude also offering the book on Amazon or iTunes?
It's issues like that every step of the way. As another example, I found EPUB looked one way on one device, but converting it to MOBI for a Kindle caused subtle changes. It's almost like browser compatibility BS all over again.
Wasn't trying to duck your question, but I basically found nothing that wrapped it all up in one easy-to-understand package. Perhaps if I make a few bucks with the first book I'll go back and write an ebook, "Ebooks for hackers" which assumes you know stuff like CSS, XML, and XHTML and instead concentrates on the other parts.
b) Today's publishing industry runs on the set of business practices that didn't cause someone [else] to go bust at some point over the past 150 years. It may look archaic and weird, but it's that way for a whole bunch of reasons that looked good at some time.
More here: http://www.antipope.org/charlie/blog-static/2010/04/common-m...
Writing a chapter is quite a bit of work, so a book must be quite an undertaking. I feel that it's worth doing, though. Writing anything -- a design spec, an email, a story from your past, etc -- forces you to coalesce and clarify thoughts that have floating around your brain. I gained new perspective on events that I thought I had a complete handle on years earlier.
BT: http://oreilly.com/catalog/9780596518028
http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Dap...
Which is not to say that I haven't written technical books, back in the day:
http://www.amazon.com/Web-Architects-Handbook-Charles-Stross...
I'm not self-published -- I've got Ace (aka part of Penguin USA), Orbit (aka Hachette) and Tor (aka Holtzbrinck) as my publishers.
Yes, I do this for a day job.
http://www.amazon.com/Authoritas-Students-Admissions-Foundin...
It's self-published through my company, Think Computer Corporation, under the Think Press label.
The web-based version contains links on a page-by-page basis to primary source documents and is available free here:
http://www.aarongreenspan.com/authoritas.html
In case you're curious, my response to Peter Cooper's Amazon.com comment is here:
http://www.aarongreenspan.com/cooper.txt
I've written more about the numbers and process here:
http://news.ycombinator.com/item?id=870015
The parent thread by Peter Cooper is very interesting too: http://news.ycombinator.com/item?id=869106
http://www.keenzo.com/showproduct.asp?ID=2328952
I wish I had written it in English, it would have helped 10 times as many people and opened 10 times as many doors. Money would have been better too.
I'm writing other stuff now, but it's fiction and as of yet unpublished (and unattempted to). In due time.
1. When You Sign a Business Contract: A Final Pre-Flight Checklist. http://goo.gl/2PbFM This is a $9.99 PDF, downloadable from e-junkie.com. It lists five points that anyone who signs a contract should check to reduce the chance of personal liability, jail time, dangerous provisions, etc. The extensive notes contain numerous real-life stories. The five-point checklist itself and a link to buy the book are posted on my blog.
2. The Law and Business of Computer Software. http://goo.gl/OnqrO This was a treatise for lawyers, first published in 1990 and still in print. I stopped doing the annual updates about 10 years ago; another author's name is on the second edition.
Not a day job.
Do consulting and bootstrapping work as my main source of income.
http://www.apress.com/microsoft/wpf/9781430237471
It's a lot of work, but it's worth it - I've been working with this technology (Rx) for two years now and I think it's a huge step forward yet very few people understand it. The book will help bring Rx to the masses which is definitely exciting.
I don't think I've got another book in me. For now I enjoy writing technical articles, mostly for IBM developerWorks. See http://seanwalberg.com for the list of articles.
I take a lot of the hassle out of writing by doing two things: I mostly just write about things I have used for work and only write about things that really catch my interest.
I mostly write about artificial intelligence, Java, Lisp, and Ruby.
http://www.stanford.edu/~jashen/home.html http://www.lulu.com/product/paperback/stanford-spirit/448066
My second book is Economtricks: http://goo.gl/Fd8tW took only a year to write. I got some things off my chest. Not as rewarding, financially or personally.
http://oreilly.com/catalog/9780596101152
Definitely a lot of work and a worthwhile pursuit.
http://onyxneon.com/