Typical startup flow is like this: 1. build an app with the most rapid way (forget about best coding practices etc) 2. get traction 3. get funding 4. pay someone smarter to refine the code and make it scale
Even in the 'right way' scenario, people often defer optimization as "premature optimization is the root of all evil". But developing in GAE forces us to optimize from the beginning (e.g. must use index, must denormalize, must make program startup fast). That's not all bad, but I think it's making us slow. Partly because we' accustomed to develop "normal" apps (use SQL with all its bells and whistles, use Spring for Java, freedom of framework/stack, etc). What do you guys think? On Nov 4, 6:29 am, Sun Jing <[email protected]> wrote: > I think there must be a way to optimize, but I agree with you that it's not > worth redesigning and rewriting your site. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
