Off topic: Startup vs Established culture. I do have to say that startups from a managers perspective is easier.. You have a carrot and a stick built in. Carrot = "Do great and we will all be rich" and stick = "Fail and we will run out of money and all be homeless on the street" that gives you an interesting team dynamic, vs in a large established org. you have "do well and you will get a bonus relative to how well you did vs your peers" or stick "fail and in 18 months after 3 bad reviews we'll consider letting you go"
From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Ikai Lan (Google) Sent: Thursday, June 09, 2011 2:40 AM To: Google App Engine Subject: Re: [google-appengine] Re: Register Article on GAE Talking about yourself, Robert? =) 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 Thu, Jun 9, 2011 at 12:15 AM, Robert Kluin <robert.kl...@gmail.com> wrote: I've got to say, I really like Typhoon AE's approach for this purpose. Swap the 'fake' stubs out in the SDK for one that actually do stuff. Most of the GAE APIs are quite nice, simple but quite powerful. If your datastore access is that thin, I guess you just need something that implements some type of simple get and put? When I read that blog post it just made me think that some people probably prefer startup type culture. Robert On Wed, Jun 8, 2011 at 11:43, Brandon Wirtz <drak...@digerat.com> wrote: > Actually it's 3 but who's counting. :-) > > No it's about 6, and I have a function that handles my most common datastore > reads and writes so that when I port to a different data store I swap from > GAEData.py to MSSQL.PY or AWSMYSQL.PY in the import and the code base > doesn't have to change. > > I do the same thing with URLFetch and MemCache. > > > > -----Original Message----- > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer > Sent: Wednesday, June 08, 2011 12:51 AM > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Re: Register Article on GAE > > If you can implement your data access with 6 lines of code, I'm jealous!! > > Jeff > > On Tue, Jun 7, 2011 at 10:54 PM, Brandon Wirtz <drak...@digerat.com> wrote: >> You are only locked in if you don't build your own functions to talk >> to datastore. >> >> If you have a "Get Data" function you can swap 6 lines of codes with >> the 6 lines you need for MSSQL when you move to Azure, or the 8 lines >> for LAMP, >> >> >> -----Original Message----- >> From: google-appengine@googlegroups.com >> [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer >> Sent: Tuesday, June 07, 2011 10:39 PM >> To: google-appengine@googlegroups.com >> Subject: Re: [google-appengine] Re: Register Article on GAE >> >> I assume he found my name on this group, but I didn't ask. Presumably >> he's reading this thread :-) >> >> He seemed like a nice guy. I thought the article was pretty good, and >> casts GAE in a favorable light. Bringing up MongoDB and HBase makes >> sense; along with GAE these are the three horsemen of the SQLpocalypse. >> >> Most of the article dealt with the question of being "locked in" to >> Google and having to deal with high-sigma events like repricing of the >> whole business. When I talk to people who haven't drank the GAE >> koolaid, this is the #1 thing they always bring up... and I have to >> admit that it's a fair criticism, especially in light of recent >> events. I don't think it's compelling compared to the terrific >> benefit of being able to develop, deploy, and scale a app without >> hiring an ops team, but I don't expect this criticism to go away. >> >> Jeff >> >> On Tue, Jun 7, 2011 at 7:30 PM, Brandon Wirtz <drak...@digerat.com> wrote: >>> Metz reached out to me after finding me on the group, but I don't >>> think I >> said enough things that could be spun as bad so none of them made it >> in the article. >>> >>> Sent from my Samsung EpicT 4G >>> >>> "Ikai Lan (Google)" <ika...@google.com> wrote: >>> >>>>I think it's kind of neat how I recognize every single name in that >> article. >>>>Did the author find you guys via Google Groups? >>>> >>>>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 Wed, Jun 8, 2011 at 5:47 AM, Andrei <gml...@gmail.com> wrote: >>>> >>>>> There is another article about Android >>>>> >>>>> http://www.computerworld.com/s/article/9217400/Major_damages_sought >>>>> _ in_Oracle_Google_patent_dispute_ Does this make any difference >>>>> for GAE? Probably not? >>>>> >>>>> On Jun 7, 9:59 am, Joshua Smith <joshuaesm...@charter.net> wrote: >>>>> > http://www.theregister.co.uk/2011/06/07/inside_google_app_engine/ >>>>> > >>>>> > Nice overview, and I didn't see any glaring errors. I'll be >>>>> > keeping a >>>>> link to this to pass along whenever anyone asks me what GAE is (and >> isn't). >>>>> An interesting observation was that many apps spill into non-GAE >>>>> infrastructure when they need some functionality that GAE doesn't > offer. >>>>> That's true of several of our apps: one of my apps interfaces with >>>>> S3 heavily because I wrote it before BlobStore existed; another >>>>> uses GAE only as a massively scalable front-end "lobby" and >>>>> scheduler, for access to non-GAE servers (in a private data center, >>>>> and in EC2 when the private data center fills up). >>>>> > >>>>> > Also, it was interesting to see the coverage of App Scale. I was >>>>> familiar with AETyphoon, but not App Scale. Nice to know there are >>>>> options if google makes some really bad decisions about their >>>>> pricing model in the coming months. >>>>> > >>>>> > -Joshua >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Google App Engine" group. >>>>> To post to this group, send email to google-appengine@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>>>> google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/google-appengine?hl=en. >>>>> >>>>> >>>> >>>>-- >>>>You received this message because you are subscribed to the Google >>>>Groups >> "Google App Engine" group. >>>>To post to this group, send email to google-appengine@googlegroups.com. >>>>To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . >>>>For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups >> "Google App Engine" group. >>> To post to this group, send email to google-appengine@googlegroups.com. >>> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . >>> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Google App Engine" group. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> >> -- >> You received this message because you are subscribed to the Google Groups > "Google App Engine" group. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . >> For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . > For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com <mailto:google-appengine%2bunsubscr...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
