Announcing Bulletproof Ajax

When I wrote DOM Scripting, I can’t say it was the most pleasant experience. I found the act of writing to be quite laborious. As anyone who has written a book will tell you, it’s a hell of a lot of work.

But then when the book was finished and I finally held it in my hands, I experienced a great feeling of satisfaction. Once the reviews started coming in — mostly more than favourable — I felt even better. Before too long, I had almost forgotten the pain that had gone into writing the thing in the first place.

It was while I was in this vulnerable state of the newly-chuffed author at last year’s South By SouthWest that I was wined and dined by a charming representative from New Riders. Before I knew it, I found myself agreeing to write another book, one about Ajax this time.

Once the contract was signed, I was back behind my laptop staring at a blank Word document. That’s when I started remembering the pain of writing the first book. Bugger.

Fast forward to today. I’m done. The book is called Bulletproof Ajax and it will be released in one month’s time.

As yet, I don’t have a physical copy in my hands but already I’ve got that warm glow of achievement. I’m really, really pleased with how the book has turned out.

Now, here’s the thing: I think that people will either love this book or hate it. I didn’t write a typical programming book. Instead, the book has a strong sense of narrative and a distinctive tone of voice. I’m hoping that this will appeal to a lot of people but I expect it’s equally likely that it will put other people off.

I wouldn’t have written this book if I didn’t feel there was a need for it. On the face of it, another book on Ajax doesn’t seem to be filling a niche. After all, there’s no shortage of Ajax books out there. But most of those Ajax books are written for programmers. Generally they’re aimed at server-side programmers well-versed in a “proper” programming language like Java, and who must now come to grips with JavaScript.

Bulletproof Ajax is different. It’s aimed at front-end developers and designers: the kind of people who are already well-versed in web standards; CSS, (X)HTML, and maybe a dab of JavaScript. But it’s certainly not aimed at hardcore programmers.

Just to be clear: this book is not a cookbook of code. Yes, there is code in there to illustrate the concepts but it’s the concepts that are really important. The code is meant simply as a starting point. I go into far more detail on the design challenges and philosophical implications of Ajax. That’s why I think people will either love this book or hate it.

Personally, I love it… but then I may be a little bit biased—like a parent talking about how special their child is.

I’ve created a website to go with the book. It’s got the introduction, the table of contents and the code samples. Rather than start up yet another blog, I’m going to continue talking about Ajax and JavaScript on the DOM Scripting blog and then pull in the latest entries on the front page of the Bulletproof Ajax site.

Oh, by the way, about the title… I have Dan’s blessing. I just thought it was such a great adjective to apply to my approach to Ajax that it fit like a glove. So minus points for originality but plus points for accuracy.

Bulletproof Ajax is available to pre-order from Amazon. Some of the details listed on the Amazon page have been plucked from thin air and will get updated soon: the book is closer to 200 pages than 300.

If the release date listed on Amazon is correct, then the book will be available just in time for Valentine’s day so you can go ahead and get a book on Ajax for that someone special in your life. XMLHttpRequest is a geek’s best friend.

Have you published a response to this? :

Previously on this day

16 years ago I wrote Shooting the band

I spent the wee hours of last night honing my Photoshop chops.

18 years ago I wrote The Lord of the Rings : The Fellowship Of The Ring

I’m going to chime in pretty late in the day with my thoughts on The Fellowship Of The Ring.

18 years ago I wrote "Google effect" reduces need for many domains

Here’s an upbeat article from Dan Gillmor.