Shared publicly  - 
 
Programming Google App Engine, 2nd edition, is draft complete!  I submitted the last of the new sections yesterday.  There's still a bunch of editing and testing to do, but the outline is final and there's text everywhere.  Early Release subscribers should get an update notification sometime in the next week or so, and of course you'll get the final version in the end.  The production process (editing, layout, illustration, indexing) takes a couple of months, so we're looking at a street date of late September or early October.

The draft PDF is 497 pages.  Over 50% of that is new or rewritten material.  More information on what's new, including the final chapter list:
  http://ae-book.appspot.com/blog/entry/2nd_Edition_is_Draft_Complete
18
4
Eric James Soltys's profile photoIstván Maczkó's profile photoEdouard Marquez's profile photoPatt K. (ppattern)'s profile photo
14 comments
 
It must take forever to write a 497 page book.
 
Pretty close to forever.  Most of the time is spent worrying about how you should be working on the book while you're doing other things.  The actual writing happens in spurts, with a big push at the end.  The 1st edition, accounting for about 350 pages of writing, was 18 months of calendar time with many months of Sundays dedicated to the task.  The 2nd edition was another 250 pages (100 rewritten, 150 new), and about 12 months on the calendar, with three weeks of solid writing (10+ hrs/day, 7 days/week) at the end.  I hope with more practice I can learn to pace it better, but I tend to ruin myself with this sort of thing.

Shorter books are more practical to write, and thankfully there's a growing market for short tutorial/overview books on technical topics.  We no longer need computer books to be large to be authoritative.  I hope my 500 pager is all useful and I don't regret the length.  But to any other professional considering writing their first book, I'd recommend starting small.  A 200-page book can sell for $20 and be exceptionally valuable.
徐烺
 
read book to climb GFW
 
What was final decision on datastore api chapter? 
 
+Matija Jerković Can you elaborate on your question? Are you asking whether a particular aspect of the datastore API is covered?  If you're asking about the new Python ndb library, I decided to leave it out because it's relatively new and I didn't have time to write it up properly.  But pretty much every other aspect of the datastore is covered, in six chapters.
徐烺
 
big query api?
 
No direct coverage of the BigQuery API.  If I covered other Google products in the book, I'd never be able to stop writing.  :)  I had planned a chapter on calling Google services from App Engine, but it was cut under time pressure.
 
Wasn't there some 'voting' for datastore api coverage? Kind of only low level or some higher level like jpa or even objectify.
 
Dan, I am looking forward to read your book even though it's a bit early for me considering other technical subjects such as HTML5, CSS3 JS/DART, Python 2.7/Django/Web2py I still have to tackle. Never the less, to me it looks like you have written the GAE "Missing manual". One of the subject I am looking forward to better understand is the Datastore. This comment from someone who used to be a Unix/C/RDBMS developer.
 
Dan, looks like your book will be available in multiple formats and from many sources. Will that include the Google Play Book store?
 
Hi, I got the first edition ebook (I imagine is out of date by now) There doesn't seem to be any discount for getting a new edition?
As to the new edition I would like to have a major chapter dealing with integration with android, as well as settling on a "boilerplate" or basket of technologies like https://github.com/coto/gae-boilerplate 
Thanks for putting a book together, I look forward to reading!
 
+Matija Jerković The main result of that poll question was the demotion of JPA in the tutorial in chapter 2.  It's not completely removed, but many of the new datastore features don't have JPA equivalents, and the "low-level" datastore API is much more compelling now than it was three years ago.  I wanted very much to add material on Objectify, but as with ndb, there wasn't time.

+Jean-Claude Noel The book does cover the datastore extensively, so hopefully this'll be what you're looking for!  I see the 1st edition in the Play store, so I'd imagine the 2nd edition will show up there in October.  If you buy directly from O'Reilly's website, you get DRM-free ebooks in multiple formats including epub and PDF.  I keep my O'Reilly epub library on my Nexus 7, and even a few titles on my phone.

+Peter Retief There's no official upgrade discount between editions, but O'Reilly does have a satisfaction guarantee, so you might ask them about it.  The 2nd edition outline is final, so no time for an Android chapter I'm afraid.  There are several good I/O videos and articles on Android and App Engine.  Here's one from last year: http://www.google.com/events/io/2011/sessions/android-app-engine-a-developer-s-dream-combination.html
 
Hey Dan, have you posted the code for your second edition yet?  I looked around and did not see it on your appspot page.  I just purchased your second edition book and am looking forward to digging in on the Python 2.7 features.  Thanks.
 
+Brandon Hedge I'm still working on the 2nd edition sample code, as part of the QA process over the next couple of weeks.  I hope to have it done before the book itself is out in September.  I'll post here and to the book blog when it's ready.  Thanks for the interest!
Add a comment...