Writing a book is no easy task, especially a technical one.  In my case, I'm writing the second edition to my relatively-popular "Beginning .NET Game Programming in C#" book.  The challenge is that this is looking more and more like a rewrite than a second edition.  Why?  Let's look at the list:

Originally, I had planned to have the book on the shelves by the end of this year, but I need to balance that with offering a book that has relatively stable examples.  There's nothing more frustrating than buying a book and having it become horribly outdated in less than a year.  That's why I try to keep the source code printed in the book as minimal as possible, and instead point you to the downloadable source.  In addition to the potential technical delays, my new job is going to keep my hands VERY full over the next several months.

 

Lastly, at the moment, I'm sticking to a C# version for now, but my publisher is asking (more like begging) that I consider a VB version, as well as a C++/CLI version.  While this is interesting, I just don't have enough visibilty into the demand for something like that.  I did a VB version of my first edition, which hasn't seen a lot of demand.