Hey Drew, Yeah, the guide wasn't going to be so much a blind tutorial as a roadmap not dissimilar to what other community members here have shared. For instance, it would say:
1. Step 1 - learn about App Engine's limits (link to pages about various quotas, limits, etc. No sockets, no file access) 2. Step 2 - learn about the datastore (links to pages about learning about the datastore, plus some to-be-written articles by members of our team and community about sharding, persistence in a denormalized world, etc) 3. Step 3 - Learn about unit testing 4. Production checklist: - enabled billing? - load test? - backed up source code? (Surprised? Search this group for "help help I lost my source code can I download it from GAE") - ran AppStats a few times? Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Mon, Apr 4, 2011 at 5:15 AM, Drew Spencer <[email protected]> wrote: > Hey Ikai, > > Great to hear that. We all know how hard it is to see something through > someone else's eyes when you know it so well yourself. > > I think that when learning something from scratch like this it's good to > try and strike a balance between just following tutorials blindly, and doing > your own investigation and learning. Sometimes I find that I can accomplish > a lot with tutorials, but then discover that they were teaching me to work a > certain way that wasn't so clear at the time. On the flipside, throwing > yourself in at the deep end without guidance can be a waste of time too. If > I hadn't created this thread I would probably be spending this week learning > JDO instead of studying the datastore, just because the tutorial introduces > JDO, which is understandable, as a beginner's tutorial doesn't need to be > confusing people with third party libraries and so on. > > For me, knowing what choices are available is key, as I can then work out > which are best for me before going down any blind alleys. The guide sounds > like a great idea - perhaps it could branch off in particular directions > depending on the type of app the user is creating? I know that some of the > above suggestions are not for me (ultra-high traffic levels are unlike to be > a problem for instance) as the app is only for internal use and numbers will > be in the tens to hundreds. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
