Write the introduction first?

I’m working on the introduction chapter for “Begin to code: Building Apps and Games with the Cloud”. It was suggested that I should write the introduction when I’ve finished the entire text. That way I’ll know exactly what ended up in it. I quite like this idea, but I think I’ll try and write the introduction first. I think it is better to have an idea where you are going before you start. And I can always revise it later…

Yet another book

I’m writing another book. You might wonder why I’ve just signed up to spend 6 months of my life thinking about nothing but JavaScript and deadlines, but I happen to like writing. So there.

The new book has the title “Begin to Code – Building Apps and Games in the Cloud”. It’s a follow up for “Begin to Code with JavaScript” with the aim of turning the reader from a programmer to a programmer who knows how to use the cloud.

I’ve already had a lot of fun putting together the overview and roughing out the sample projects. And I’m really going to enjoy turning out the text. Really