What you can learn by writing a book

At some point in time, I thought I will actually never be able to put it in writing, but here it is: I managed to finish the book on many-core programming I’ve been working on (with two co-authors) for the past one and a half year – complete with references, figures and word index. It’s now submitted to the publisher, so stay tuned for a release in June.

It was a one of a kind experience. I learned a lot on the technical side but, even more importantly, a lot of the” do:s and don’t:s” of writing a book. Working on a book is a solitary experience and – especially towards the end – a race against the clock and number of pages. You just sit in front of your screen and type and type and type, with the sword of public criticism over your head: every mistake you make will be criticized, perhaps ridiculed. You try to get the text in shape, only to realize, at the end, that the most time-consuming and dull work is to actually get your references, keywords and figures in shape – let alone proof-reading and fixing the raw text you produced.

Would I do it again? Probably yes, but certainly not right how. Will I read it, once out in the wild?

Don’t know. Let me know if it’s worth reading 😉

2 Responses to “What you can learn by writing a book”

  1. Softtalkblog says:

    Congratulations! Writing a book can be an exhausting but ultimately rewarding experience. What’s the title and who is the publisher of your book?

  2. Vajdi says:

    Thank you!
    It’s “Programming Many-core Chips”; it was commissioned by Springer. It should show up in on-line stores for pre-order in the coming weeks (due to appear in Q2)